click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <>
Subject [jira] Commented: (CLK-418) Tomcat redeployment JAR locking
Date Mon, 20 Jul 2009 20:58:14 GMT


Bob Schellink commented on CLK-418:

The antiResourceLocking is a configuration option for Tomcat and won't work with Glassfish.
In fact the context.xml file is Tomcat specific. I don't think other servers use it.

I'm quite surprised you see locking issues on Solaris. I thought only Windows lock files.

Perhaps we should introduce the ability to switch off auto-deployment in click.xml keeping
in mind that CLK-564 provides alternative solutions to the deployment problem.

> Tomcat redeployment JAR locking
> -------------------------------
>                 Key: CLK-418
>                 URL:
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.5 RC2
>         Environment: Tomcat 5.5.25, Click 1.5-M2, JDK 1.5, click-examples
>            Reporter: Malcolm Edgar
> I am seeing intermitt Tomcat auto deployment issues, where there is a lock on a JAR in
click-examples/WEB-INF/lib/ which cannot be deleted. 
> This issue occurs regularly for a period and then does not occur at all.  The JAR being
locked on is fairly random.  Sometimes spring-*.jar or log4*.jar
> To fix this issue you stop Tomcat, delete the click-examples directory, and then restart
Tomcat. This is not a good development experience.
> This Tomcat behaviour is similar to CLK-82 when Click was scanning the classpath for
files named "/click-controls.xml". In these cases however the JAR being locked on was always
> Commenting out XmlConfigService#deployFilesInJars() fixes this issue as does setting
antiResourceLocking="true" in the click-examples/META-INF/context.xml
> <Context
>    path="/click-examples" 
>    reloadable="true"
>    antiJARLocking="true"
>    antiResourceLocking="true">
>    <ResourceLink 
>       name="users" 
>       global="UserDatabase"
>       type="org.apache.catalina.UserDatabase"/>
> </Context>
> I can see two solutions to this problem. First is we heavily document deployment options
on application servers:
> * Tomcat set    antiJARLocking="true" and  antiResourceLocking="true"
> * WebLogic unpack any click resources into your web applications /click directory before
> The other option is to make this configurable JAR deployment configurable:
>   <click-app deploy-jar-resources="true">
>   ..
>   </click-app>
> Otherwise we will get continual issues raised about Tomcat hot deployment.
> Note this issue does not occur on JBoss as they create a new webapp instance each time
you deploy an application.  This is a mode you can use in Tomcat as well (since JBoss uses
Tomcat internally) but it is not the default Tomcat configuration.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message