RE: Analyzing Tomcat related VM crash?

2009-05-12 Thread Peter Crowther
> From: Rainer Jung [mailto:rainer.j...@kippdata.de] > Look for a GC fix (1.6.0_13), or try the child vm, or try switching to > another GC algorithm, like CMS. (Coming to the thread late, sorry if this has all already been said). Also consider bad RAM, or memory corruption caused by some native c

Re: Analyzing Tomcat related VM crash?

2009-05-12 Thread Rainer Jung
On 12.05.2009 01:13, Andre-John Mas wrote: > I have added the details to the end of this e-mail. > # SIGSEGV (0xb) at pc=0x06546578, pid=7456, tid=2349013936 > Current thread (0x08060800): GCTaskThread [stack: > 0x8bfb1000,0x8c032000] [id=7459] > Other Threads: > 0x8bd97800 VMThread [stack:

RE: Analyzing Tomcat related VM crash?

2009-05-11 Thread Caldarale, Charles R
> From: Andre-John Mas [mailto:aj...@sympatico.ca] > Subject: Re: Analyzing Tomcat related VM crash? > > I have added the details to the end of this e-mail. If the hardware tests don't find anything, try running the JVM in client mode rather than server. Historically, the se

Re: Analyzing Tomcat related VM crash?

2009-05-11 Thread Andre-John Mas
On 11-May-2009, at 18:59, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André-John, On 5/11/2009 6:48 PM, Andre-John Mas wrote: We have recently put into production a Tomcat 5.5.27 based web site, using JDK 1.6 (JDK 1.6.0_12-b04 on RedHat Linux). We have spent mo

Re: Analyzing Tomcat related VM crash?

2009-05-11 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André-John, On 5/11/2009 6:48 PM, Andre-John Mas wrote: > We have recently put into production a Tomcat 5.5.27 based web site, > using JDK 1.6 (JDK 1.6.0_12-b04 on RedHat Linux). We have spent months > developing and testing the site, both by us and t

Analyzing Tomcat related VM crash?

2009-05-11 Thread Andre-John Mas
Hi, We have recently put into production a Tomcat 5.5.27 based web site, using JDK 1.6 (JDK 1.6.0_12-b04 on RedHat Linux). We have spent months developing and testing the site, both by us and the customer, and experienced no VM crashes. Now that we are in production we find the VM is cras