[jira] Created: (STR-3143) In Tomcat, when restarting a webapp, the struts-core-1.3.8.jar remains "in-use" preventing dynamic redeployment

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


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.

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

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

    Fix Version/s: 1.3.10

May be fixed in 1.3.10. Give it a try.

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

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

Niall Pemberton commented on STR-3143:
--------------------------------------

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.

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

niallp@... 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: niallp@...):
    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.

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

Paul Benedict commented on STR-3143:
------------------------------------

David, can you tell me if the issue is still outstanding?

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

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

Matthieu Chase Heimer commented on STR-3143:
--------------------------------------------

Sounds like the standard antiResourceLocking and antiJARLocking settings that are always needed on Windows http://tomcat.apache.org/tomcat-5.5-doc/config/context.html#Standard%20Implementation

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

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

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

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?

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

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

    [ 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:37 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 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.

      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?

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

    [ 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:53 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 and also a /conf/Catalina/localhost/context.xml.default 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 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.
 

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

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

Niall Pemberton commented on STR-3143:
--------------------------------------

David,

Sorry I forgot that the issue I mentioned also affects Commons Validator and Commons Chain - which also use Digester to parse their XML config files - but on this front theres good and bad news:

Commons Validator
----------------------------
 * The bad news is the change to use the new constructors provided by Digester 1.8 has not yet made it into a Validator release (see http://issues.apache.org/jira/browse/VALIDATOR-211 )
 * The good news is the same fix applied in Digester 1.8 was also applied in Validator 1.3.1 (see http://issues.apache.org/jira/browse/VALIDATOR-209 ), so if you're not yet using Validator 1.3.1 can you try upgrading to that version
 * http://commons.apache.org/validator/

Commons Chain
------------------------
 * The bad news is the change to use the new constructors provided by Digester 1.8 has not yet made it into a Chain release (see http://issues.apache.org/jira/browse/CHAIN-33 )
 * I will try and find time to do a Commons Chain release soon (but no promises!) - in the meantime I have built the current chain which you could try out - http://people.apache.org/~niallp/chain-1.2-20080520/
 * ALternatively if you don't want to use those versions, you could check out the source yourself from subversion and build using maven 2 http://commons.apache.org/chain/source-repository.html
 * http://commons.apache.org/chain/

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

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

Matthieu Chase Heimer commented on STR-3143:
--------------------------------------------

You're probably going to have to upgrade to Tomcat 5.5 and put in both antiResourceLocking and antiJARLocking in.
See: http://wiki.apache.org/tomcat/FAQ/Windows#Q5

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

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

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

Paul Benedict commented on STR-3143:
------------------------------------

Niall, is Chain 1.2 expected soon? I will make sure the Struts POM is updated for it, if so.

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