You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2008/05/21 05:49:05 UTC

[jira] Updated: (STR-3143) Struts jar remains "in-use" preventing dynamic redeployment

     [ https://issues.apache.org/struts/browse/STR-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict updated STR-3143:
-------------------------------

    Priority: Critical  (was: Minor)
     Summary: Struts jar remains "in-use" preventing dynamic redeployment  (was: In Tomcat, when restarting a webapp, the struts-core-1.3.8.jar remains "in-use" preventing dynamic redeployment)

> Struts 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: Critical
>             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.