Chris,
I find it hard to believe two brand new machines with different processors,
etc. would have a hardware problem that showed itself in exactly the same
way. Further, I have run memTest86 for 30 hours on one of the servers and
it showed nothing (although, as Chuck pointed out, the test may not have
handled the cores correctly or may not have changed the temperature
sufficiently to cause the problem we are seeing.) I have not found a mem
test specifically for 64 bit processors.
Thanks,
Carl
----- Original Message -----
From: "Christopher Schultz" <ch...@christopherschultz.net>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Friday, February 12, 2010 5:26 PM
Subject: Re: Tomcat dies suddenly
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Carl,
On 2/12/2010 4:44 PM, Carl wrote:
Now, this is embarrassing: I just checked the other server and it also
has a core file with the date and time of the last failure in the
tomcat/bin directory. And, it shows a seg fault at exactly the same
code.
This might be a winner... we certainly know it killed the java process.
So, this now, to me, narrows this down to two possibilities:
1. A JVM bug
2. A hardware problem
That is, if you really aren't running any native code.
But, if you were, it would be showing up in the code dump, right?!
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkt11YMACgkQ9CaO5/Lv0PC/ZwCcCdB3k1ARO5uhxneWilt3wkox
n/4AniRJb/t3Xd9FgKQecXHN7UyFP5RQ
=s/EK
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
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
