Re: JAR files still locked after Context.stop()

2010-04-29 Thread Jamie
Hi Chuck I'll try... I think there is a JAR registration issue with Javamail. At least, I found an article on the Internet that talks about it. On 2010/04/27 10:52 PM, Caldarale, Charles R wrote: From: Jamie [mailto:ja...@stimulussoft.com] Subject: Re: JAR files still locked

RE: JAR files still locked after Context.stop()

2010-04-27 Thread Caldarale, Charles R
> From: Jamie [mailto:ja...@stimulussoft.com] > Subject: Re: JAR files still locked after Context.stop() > > I figure out that it is only the Javamail mail.jar file that > is locked. For some reason, Windows wont let go of it, but all > other appear to be fine. You could alwa

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Jamie
...@stimulussoft.com] Subject: Re: JAR files still locked after Context.stop() I've check them out in YourKit profiler thoroughly. All threads in the main web application are exiting cleanly. Not threads, classes. Use the heap profiler to see if any of your webapp's classes or

RE: JAR files still locked after Context.stop()

2010-04-27 Thread Caldarale, Charles R
> From: Jamie [mailto:ja...@stimulussoft.com] > Subject: Re: JAR files still locked after Context.stop() > > I've check them out in YourKit profiler thoroughly. All threads in the > main web application are exiting cleanly. Not threads, classes. Use the heap profiler t

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Konstantin Kolinko
2010/4/27 Jamie : > > I've check them out in YourKit profiler thoroughly. All threads in the main > web application are exiting cleanly.  Is there is a way to call the > WebAppClassloader to unload a particular JAR file? > JAR file, as well as any opened file, is an OS resource. Just GC() is not e

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Jamie
to:ja...@stimulussoft.com] Subject: Re: JAR files still locked after Context.stop() I can see in the profiler that there are no running threads pertaining to the main web app. What about classes related to the webapp? There's no guarantee that the Tomcat kludge for memory leaks has found

RE: JAR files still locked after Context.stop()

2010-04-27 Thread Caldarale, Charles R
> From: Jamie [mailto:ja...@stimulussoft.com] > Subject: Re: JAR files still locked after Context.stop() > > I can see in the profiler that there are no running threads pertaining > to the main web app. What about classes related to the webapp? There's no guarantee that th

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Jamie
Konstantin As a matter of fact, yes, I do have className="org.apache.catalina.core.JreMemoryLeakPreventionListener" /> in server.conf and it does not appear to helping. I still cannot delete any JAR file after called Context.stop(). I can see in the profiler that there are no running threads

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Konstantin Kolinko
2010/4/27 Jamie : > Konstantin > > I just tried 6.0.26 and no joy. JARs remain locked by Windows. In the auto > update application I call context.stop() immediatel and System.gc() but alas > all JAR files are locked. Any other ideas? > > Jamie > > On 2010/04/27 04:17 PM, Konstantin Kolinko wrote: >

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Jamie
Konstantin I just tried 6.0.26 and no joy. JARs remain locked by Windows. In the auto update application I call context.stop() immediatel and System.gc() but alas all JAR files are locked. Any other ideas? Jamie On 2010/04/27 04:17 PM, Konstantin Kolinko wrote: 2010/4/27 Jamie: Hi Kons

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Konstantin Kolinko
2010/4/27 Jamie : > Hi Konstantin > > Thanks. I'll give that a try. Can you confirm whether the options you were > referring to are antiJARLocking="true" antiResourceLocking="true". Is it > still necessary to specify these options in 6.0.26? > Yes, those options. In 6.0.26 you will have JreMemory

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Jamie
Hi Konstantin Thanks. I'll give that a try. Can you confirm whether the options you were referring to are antiJARLocking="true" antiResourceLocking="true". Is it still necessary to specify these options in 6.0.26? On 2010/04/27 03:45 PM, Konstantin Kolinko wrote: 2010/4/27 Jamie: Hi Ko

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Konstantin Kolinko
2010/4/27 Jamie : > Hi Konstantin > > Here you go: > > OS: Windows 7 (version 6.1.7600) > Tomcat: 6.0.20 > JRE: 1.6.0_18-b07 > > Thanks for your guidance > The latest v6 is 6.0.26. Try it. For 6.0.20 and earlier you would need additional configuration options to prevent jar locking on Windows. B

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Jamie
Hi Konstantin Here you go: OS: Windows 7 (version 6.1.7600) Tomcat: 6.0.20 JRE: 1.6.0_18-b07 Thanks for your guidance Jamie INFO: Starting Servlet Engine: Apache Tomcat/6.0.20 On 2010/04/27 03:26 PM, Konstantin Kolinko wrote: 2010/4/27 Jamie: I am using the latest version of Tomcat (v6

Re: JAR files still locked after Context.stop()

2010-04-27 Thread Konstantin Kolinko
2010/4/27 Jamie : > I am using the latest version of Tomcat (v6) > There are about 20 different releases of Tomcat v6. Which one do you use (x.y.z), or are you building it yourself? What are your operation system and Java vendor and versions? Best regards, Konstantin Kolinko --

JAR files still locked after Context.stop()

2010-04-27 Thread Jamie
Greetings I have written an autoupdate web application client whose job it is to update a main Tomcat application. When updating the application, it performs the following operations on the main web application: ((Lifecycle) context).stop(); update existing jar files delete unwanted jar files ((