[
https://issues.apache.org/struts/browse/STR-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43880#action_43880
]
[EMAIL PROTECTED] edited comment on STR-3143 at 5/17/08 2:39 PM:
---------------------------------------------------------------
There was a problem caused by a Sun bug with Digester on Windows:
http://issues.apache.org/jira/browse/DIGESTER-29
This was fixed in the Digester 1.8 release and Struts was changed to use that
version prior to the Struts 1.3.8 release:
http://svn.apache.org/viewvc?view=rev&revision=483039
What version of Commons Digester are you using? If you're not already using
Digester 1.8, then try upgrading and see if that fixes the problem:
http://commons.apache.org/digester/
was (Author: [EMAIL PROTECTED]):
There was a problem caused by a Sun bug with Digester on Windows:
http://issues.apache.org/jira/browse/DIGESTER-29
This was fixed in the Digester 1.8 release and Struts was changed to use that
version prior to the Struts 1.3.8 release:
http://svn.apache.org/viewvc?view=rev&revision=483039
What version of Commons Digester are you using? If you're not already using
Digester 1.8, then try upgrading and see if that fixes the problem.
> 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.
