jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Glass-Husain (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1301) Trouble undeploying jackrabbit-webapp from Tomcat
Date Thu, 07 May 2009 15:05:30 GMT

    [ https://issues.apache.org/jira/browse/JCR-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706931#action_12706931

Will Glass-Husain commented on JCR-1301:

This forum entry notes that (apparently) upgrading from Tomcat 6.0.16 to 6.0.18 solves the

I'm hitting the same issue with Tomcat 6.0.16.   Can anyone else verify and contradict this?

Will report back once I upgrade.

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

View raw message