-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Peter,
On 1/13/2010 8:49 AM, Peter Crowther wrote:
> Very difficult to know what the problem is. One thing you can now do
> (as you've switched to another production server) is to run a memory
> test across the "bad" server.
Usually, I would agree that physical memory problems are likely to be a
problem, but every time I've had a physical memory problem (much more
common than I'd like to admit!), the JVM has crashed in a more classic
way: that is, with an hs_log file and almost always with a SIGSEGV,
rather than this phantom thing described by Carl.
The Linux OOM killer might be a suspect, except that the process is
apparently not dying, which is very strange.
Carl: when the JVM "dies" and you use top to see free memory, does it
say that 2.4GB of memory is in use by a particular process, or does it
just appear that the memory is not "available"? If it's by a particular
process, which one? The JVM process ("/usr/bin/java" or whatever) either
does or does not exist, and if it does not exist, is it retaining
memory? If the Tomcat connectors have shut down (thereby releasing the
TCP/IP ports), but not the java process, then there should be some
indication in catalina.out that the connectors have been shut down
explicitly.
The whole thing sounds weird. :(
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAktN+ecACgkQ9CaO5/Lv0PAZzgCgsZaU16RGcs5pgsgzgLVX7q0W
8xcAnRUb1Zl+0PY6+Umk8nQAEagfl/Su
=RA9e
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
