[
https://issues.apache.org/struts/browse/STR-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43903#action_43903 ]
dtclemens edited comment on STR-3143 at 5/20/08 8:38 AM:
-------------------------------------------------------------
Thank you for three helpful responses.
Niall: this sounds very relevant, but I confirmed we are already using Digester 1.8. I checked both the webapp jars and the common/lib just in case.
Paul: I was not able to figure out how to download 1.3.10, but I tried the 1.3.9 jars and found the same problem. I would still like to test 1.3.10 if you can tell me how to get it, but if it does solve the problem, I should still be hesitant to deploy an alpha version in production with thousands of users, right?
Matthieu: We do not declare each context explicitly, but I created a Tomcat/conf/context.xml file with what I hope is a common Context declaration that will be used by all dynamically deployed contexts, with antiJARLocking="true". I had high hopes, but this did not solve the problem. The struts-core-1.3.9.jar was the only file that could not be deleted. Do you think I should need to have specific Context descriptors for each webapp, in each .war?
Thanks again for your collective help.
was (Author: dtclemens):
Thank you for three helpful responses.
Niall: this sounds very relevant, but I confirmed we are already using Digester 1.8. I checked both the webapp jars and the common/lib just in case.
Paul: I was not able to figure out how to download 1.3.10, but I tried the 1.3.9 jars and found the same problem. I would still like to test 1.3.10 if you can tell me how to get it, but if it does solve the problem, I should still be hesitant to deploy an alpha version in production with thousands of users, right?
Matthieu: We do not declare each context explicitly, but I created a Tomcat/conf/context.xml file with what I hope is a common Context declaration the will be used by all dynamically deployed contexts, with antiJARLocking="true". I had high hopes, but this did not solve the problem. The struts-core-1.3.9.jar was the only file that could not be deleted. Do you think I should need to have specific Context descriptors for each webapp, in each .war?
Thanks again for your collective help.
> In Tomcat, when restarting a webapp, the struts-core-1.3.8.jar remains "in-use" preventing dynamic redeployment
> ---------------------------------------------------------------------------------------------------------------
>
> Key: STR-3143
> URL:
https://issues.apache.org/struts/browse/STR-3143> Project: Struts 1
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.3.8
> Environment: Tomcat 5.0, Sun Java 1.5 on Windows XP or 2000
> Reporter: David Clemens
> Priority: Minor
> Fix For: 1.3.10
>
>
> We recently upgraded from an older struts.jar to struts 1.3.8. Since then, when we try to deploy a new .war file dynamically in Tomcat, it fails because Tomcat is unable to delete just one file-- the struts-core-1.3.8.jar. That file remains "in-use" until the entire Tomcat webserver is restarted. It is as if a thread is started by Struts that does not exit nicely when interrupted. Or perhaps there is some kind of special class loader used by Struts that prevents the Tomcat webapp class loader from flushing some class from this jar.
> I'm sorry if this problem is already known, but I could not find any issues that matched.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
