[
http://jira.codehaus.org/browse/MRM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107994
]
Joakim Erdfelt commented on MRM-213:
------------------------------------
Encountered this problem not on undeploy specifically, but even Tomcat shutdown.
This prevented the proper shutdown of the JDK/JRE too. It was left running in
memory, even though the Tomcat threads were no longer running.
Tested on Windows XP (SP2) w/ Tomcat 5.0.28
Using Archiva SVN Trunk r578241
JDK 1.5.0_11
> cannot undeploy archiva webapp
> ------------------------------
>
> Key: MRM-213
> URL: http://jira.codehaus.org/browse/MRM-213
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-alpha-1
> Environment: I'm running Archiva webapp under tomcat 5.5 / windows
> 2003 server
> Reporter: nicolas de loof
> Assignee: Joakim Erdfelt
> Priority: Minor
> Fix For: 1.0.x
>
>
> I'd like to undeploy without restarting Tomcat (as I don't have admin acces
> to the server). When I undelploy archiva webapp using tomcat manager, the
> webapp/archiva directory is not removed and WEB-INF/lib still contains:
> jpox-1.1.1.jar
> plexus-container-default-1.0-alpha-10.jar
> plexus-security-authorization-rbac-store-jdo-1.0-alpha-6-20061013.204855-1.jar
> plexus-security-keys-jdo-1.0-alpha-6-20061013.204855-1.jar
> plexus-security-user-management-provider-jdo-1.0-alpha-6-20061013.204855-1.jar
> webwork-2.2.4.jar
> xwork-1.2.1.jar
> I cannot remove those jars (files locked)
> Maybe some background thread is not stopped at application undeploy ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
