struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Clemens (JIRA)" <j...@apache.org>
Subject [jira] Commented: (STR-3143) In Tomcat, when restarting a webapp, the struts-core-1.3.8.jar remains "in-use" preventing dynamic redeployment
Date Tue, 20 May 2008 21:38:05 GMT

    [ https://issues.apache.org/struts/browse/STR-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43912#action_43912
] 

David Clemens commented on STR-3143:
------------------------------------

Thank you Niall, I downloaded your new version compile of commons-chain-1.2-20080520.jar and
that did it!   Now I can dynamically redeploy-- woo hoo!

(I already had Validator 1.3.1)

And thanks to Paul and Matthieu for you help too.  I think this issue can be closed now, assuming
Chain 1.2 will go into the next Struts 1.3 release.

> 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.


Mime
View raw message