2010/1/13 Christopher Schultz <ch...@christopherschultz.net>: > 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. > [...] > The whole thing sounds weird. :(
Oh, I agree entirely - usually something will turn a reference bad and you'll get a memory access somewhere off in hyperspace during a GC. But it's an easy thing to check, and there is an (admittedly small) possibility of seeing these symptoms. Heck, with hardware errors there's a small probability of seeing pretty much *any* symptoms. - Peter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
