Re: JAR locking / Tomcat 5.5.4 / Windows
Do you know how to set the same when running Tomcat in console mode (from command prompt)? On Thu, 13 Jan 2005 10:33:15 -0800 (PST), TomK [EMAIL PROTECTED] wrote: Success! I was able to get the antiResourceLocking attribute to finally take effect with Tomcat 5.5.4. The problem is the default Windows install does not set the Working Path (viewable on the Startup/Shutdown tabs of the service manager that sits in the SysTray). Once I set the working path to the tomcat base directory, and restarted Tomcat, and deployed the WAR, the application files were copied to the temp directory and run from there, just as promised. Undeploy works fine. Interestingly, the directories created in the temp directory aren't deleted when Tomcat is shutdown, for the same reason: the jar's are locked. Dominik -- Regarding your statement that the latest CVS version does not suffer from the nasty jar locking. I'll try it out later, but are you suggesting 5.5.7 will not have JAR locking issues at all, and thus the antiResourceLocking and antiJARLocking attributes will be unnecessary?? thanks -tk TomK [EMAIL PROTECTED] wrote: Thanks very much, I'll check the latest version out and post my results, in case anyone else has this issue. -tk Dominik Drzewiecki wrote: Siarhei Dudzin wrote: Did you find a solution? FYI it has been fixed on 17/12/2004 and the latest CVS version does not suffer from the nasty jar locking. The root of the problem was the JasperLoader locking (using cached getResourceAsStream()) the jars containing jsp tag libraries. It works for me. Please do give it a spin and test for yourselves. BTW, there seems to be 5.5.7 distro coming soon. cheers, /dd On Tue, 4 Jan 2005 15:27:56 -0800 (PST), TomK wrote: I've been following the recent threads regarding JAR locking with Tomcat 5.x on Windows platforms. A few people mentioned they had been able to get either the antiJARLocking or antiResourceLocking attributes to work, so I've spent quite a bit of time trying out different scenarios and configurations, under the impression that I must be missing something simple.however, I've not yet found a situation where either attribute has any effect on deploy/undeploy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAR locking / Tomcat 5.5.4 / Windows
TomK [EMAIL PROTECTED] wrote: Dominik -- Regarding your statement that the latest CVS version does not suffer from the nasty jar locking. I'll try it out later, but are you suggesting 5.5.7 will not have JAR locking issues at all, and thus the antiResourceLocking and antiJARLocking attributes will be unnecessary?? Well, in my particular case (I have a test app using jstl fmt taglib) I no longer needed antiJARLocking. I have even explicitely set it to false in context.xml. It undeploys now whereas before having the fix applied undeploy failed. cheers /dd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAR locking / Tomcat 5.5.4 / Windows
Did you find a solution? On Tue, 4 Jan 2005 15:27:56 -0800 (PST), TomK [EMAIL PROTECTED] wrote: I've been following the recent threads regarding JAR locking with Tomcat 5.x on Windows platforms. A few people mentioned they had been able to get either the antiJARLocking or antiResourceLocking attributes to work, so I've spent quite a bit of time trying out different scenarios and configurations, under the impression that I must be missing something simple.however, I've not yet found a situation where either attribute has any effect on deploy/undeploy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAR locking / Tomcat 5.5.4 / Windows
Siarhei Dudzin [EMAIL PROTECTED] wrote: Did you find a solution? FYI it has been fixed on 17/12/2004 and the latest CVS version does not suffer from the nasty jar locking. The root of the problem was the JasperLoader locking (using cached getResourceAsStream()) the jars containing jsp tag libraries. It works for me. Please do give it a spin and test for yourselves. BTW, there seems to be 5.5.7 distro coming soon. cheers, /dd On Tue, 4 Jan 2005 15:27:56 -0800 (PST), TomK [EMAIL PROTECTED] wrote: I've been following the recent threads regarding JAR locking with Tomcat 5.x on Windows platforms. A few people mentioned they had been able to get either the antiJARLocking or antiResourceLocking attributes to work, so I've spent quite a bit of time trying out different scenarios and configurations, under the impression that I must be missing something simple.however, I've not yet found a situation where either attribute has any effect on deploy/undeploy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAR locking / Tomcat 5.5.4 / Windows
Thanks very much, I'll check the latest version out and post my results, in case anyone else has this issue. -tk didn't_get_my_coffee_this_morning_rant That I find myself saying In case anyone else has this issue is somewhat amazing to me. Either: 1) Hardly anyone is using Windows as their deployment environment for Tomcat. (I probably wouldn't be either, if I had a choice.) or 2) Those using Windows as the deploy environment aren't concerned about re-deploying applications, and are content to simply restart the server, so resource locking is not an issue. or 3) Everyone can properly edit the context.xml file, except me and 5 other people on this list. There have been quite a few posts to this list, as well as bugs opened in bugzilla reporting JAR locking (with versions 5.0.x, 5.5.x). I'm a bit disheartened by the earlier replies. Either the bug was closed as invalid, or the reply was Get yourself a better operating system, or You aren't doing it right. Given the unlikely nature of #3 above, it seems much more likely that this is indeed a bug.I hope it has been fixed. /didn't_get_my_coffee_this_morning_rant Dominik Drzewiecki [EMAIL PROTECTED] wrote: Siarhei Dudzin wrote: Did you find a solution? FYI it has been fixed on 17/12/2004 and the latest CVS version does not suffer from the nasty jar locking. The root of the problem was the JasperLoader locking (using cached getResourceAsStream()) the jars containing jsp tag libraries. It works for me. Please do give it a spin and test for yourselves. BTW, there seems to be 5.5.7 distro coming soon. cheers, /dd On Tue, 4 Jan 2005 15:27:56 -0800 (PST), TomK wrote: I've been following the recent threads regarding JAR locking with Tomcat 5.x on Windows platforms. A few people mentioned they had been able to get either the antiJARLocking or antiResourceLocking attributes to work, so I've spent quite a bit of time trying out different scenarios and configurations, under the impression that I must be missing something simple.however, I've not yet found a situation where either attribute has any effect on deploy/undeploy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAR locking / Tomcat 5.5.4 / Windows
Success! I was able to get the antiResourceLocking attribute to finally take effect with Tomcat 5.5.4. The problem is the default Windows install does not set the Working Path (viewable on the Startup/Shutdown tabs of the service manager that sits in the SysTray). Once I set the working path to the tomcat base directory, and restarted Tomcat, and deployed the WAR, the application files were copied to the temp directory and run from there, just as promised. Undeploy works fine. Interestingly, the directories created in the temp directory aren't deleted when Tomcat is shutdown, for the same reason: the jar's are locked. Dominik -- Regarding your statement that the latest CVS version does not suffer from the nasty jar locking. I'll try it out later, but are you suggesting 5.5.7 will not have JAR locking issues at all, and thus the antiResourceLocking and antiJARLocking attributes will be unnecessary?? thanks -tk TomK [EMAIL PROTECTED] wrote: Thanks very much, I'll check the latest version out and post my results, in case anyone else has this issue. -tk Dominik Drzewiecki wrote: Siarhei Dudzin wrote: Did you find a solution? FYI it has been fixed on 17/12/2004 and the latest CVS version does not suffer from the nasty jar locking. The root of the problem was the JasperLoader locking (using cached getResourceAsStream()) the jars containing jsp tag libraries. It works for me. Please do give it a spin and test for yourselves. BTW, there seems to be 5.5.7 distro coming soon. cheers, /dd On Tue, 4 Jan 2005 15:27:56 -0800 (PST), TomK wrote: I've been following the recent threads regarding JAR locking with Tomcat 5.x on Windows platforms. A few people mentioned they had been able to get either the antiJARLocking or antiResourceLocking attributes to work, so I've spent quite a bit of time trying out different scenarios and configurations, under the impression that I must be missing something simple.however, I've not yet found a situation where either attribute has any effect on deploy/undeploy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAR locking / Tomcat 5.5.4 / Windows
Re: the WAR link was stripped out in that last message. It is located here: http://www.tomk.nu/tc00/sample.war
