[
https://issues.apache.org/jira/browse/JCR-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1301.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
Assignee: Jukka Zitting
In revision 1055116 I added a DerbyShutdown listener that attempts to
automatically release all remaining Derby resources when the Jackrabbit webapp
gets stopped or undeployed. That clears many of the warnings logged by Tomcat
and gives us a clean undeploy at least on Tomcat 7.
> Trouble undeploying jackrabbit-webapp from Tomcat
> -------------------------------------------------
>
> Key: JCR-1301
> URL: https://issues.apache.org/jira/browse/JCR-1301
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-webapp
> Environment: Windows Vista, Apache Tomcat 6.0.12, Sun Java 1.6.0_03
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 2.3.0
>
>
> When testing jackrabbit-webapp for the 1.4 release, I again came across this
> issue that I've occasionally seen also before, but never qualified enough for
> a bug report.
> The Jackrabbit webapp would deploy without problems, but when I undeploy the
> webapp Tomcat fails to remove the Derby jar in WEB-INF/lib (I have unpackWARs
> enabled). This causes problems especially when I have autoDeploy enabled, as
> Tomcat then deploys the skeleton webapp right after undeployment, and the
> only way to really get rid of the webapp is to shutdown Tomcat and to
> manually remove the webapp on the file system.
> I suspect that this problem is related to Derby jar being somehow referenced
> even after the webapp is undeployed, causing Windows to prevent the jar file
> from being removed.
> Unless someone has some bright idea on how to resolve this, I'll consider
> this a known issue in Jackrabbit 1.4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
