-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saumil,
Please try to keep discussions on the mailing list to everyone can
benefit.
On 4/2/13 6:48 PM, saumil shah wrote:
For some reason ...I do not see Java process in Task Manager in
Windows, just Tomcat6 process. I am assuming killing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 4/1/13 3:52 PM, Jeffrey Janner wrote:
-Original Message- From: Daniel Mikusa
[mailto:dmik...@vmware.com] Sent: Monday, April 01, 2013 1:09 PM
To: Tomcat Users List Subject: Re: how to monitor the traffic
through the
Thanks again Chris
I did change in Tomcat 6.0/Conf/server.xml
unpackWARs=false and autoDeploy=false
but the logs still complaint about the Deploying web applications
org.apache.catalina.startup.HostConfig deployWARINFO: Deploying web application
archive
Chris,
On Tue, Apr 2, 2013 at 5:12 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I understand its not a premanent solution but as a stopgap for now
? If so , we can put it as part of daily cycle to bounce tomcat6.
If you
Hi all,
Saw this recently... Some java native code included in our tomcat
deployment contained an error, which caused a JVM segfault when a
webapp called the routine.
I was startled by the fact that this native code error brought down the
entire tomcat instance (all 15+ web apps) due to a
From: Dale Ogilvie [mailto:dale_ogil...@trimble.com]
Subject: Buggy java native call kills tomcat
My question: can we protect ourselves from total instance failure, i.e.
restrict the damage to the death of just the app calling the native
library? Is there a way to make the tomcat VM survive
