Konstantin
As a matter of fact, yes, I do have
<Listener
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 pertaining
to the main web app.
Jamie
On 2010/04/27 04:57 PM, Konstantin Kolinko wrote:
2010/4/27 Jamie<ja...@stimulussoft.com>:
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<ja...@stimulussoft.com>:
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 JreMemoryLeakPreventionListener in default
server.xml, which should be enough to prevent jar locking.
Do you have the above mentioned class in your server.xml?
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
