Re: JAR locking / Tomcat 5.5.4 / Windows

2005-01-14 Thread Siarhei Dudzin
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

Re: JAR locking / Tomcat 5.5.4 / Windows

2005-01-14 Thread Dominik Drzewiecki
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

Re: JAR locking / Tomcat 5.5.4 / Windows

2005-01-13 Thread Siarhei Dudzin
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

Re: JAR locking / Tomcat 5.5.4 / Windows

2005-01-13 Thread Dominik Drzewiecki
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

Re: JAR locking / Tomcat 5.5.4 / Windows

2005-01-13 Thread TomK
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

Re: JAR locking / Tomcat 5.5.4 / Windows

2005-01-13 Thread TomK
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

JAR locking / Tomcat 5.5.4 / Windows

2005-01-04 Thread TomK
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

Re: JAR locking / Tomcat 5.5.4 / Windows

2005-01-04 Thread TomK
Re: the WAR link was stripped out in that last message. It is located here: http://www.tomk.nu/tc00/sample.war