Christopher Schultz-2 wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Chuck, > > Caldarale, Charles R wrote: >>> From: Bill Davidson [mailto:bill...@gmail.com] >>> Subject: Fun with the JVM crashing. >> >>> I'm thinking that the JVM shouldn't be getting SIGSEGV's. >> >> You're right about that. However, it could also be an OS or hardware >> problem. You might want to run some serious memory tests on the box, >> just to eliminate the latter. > > +100! > > What is the architecture? Do you have physical access? If it's x86 and > you do have physical access, 100% you should run memtest86+ against it. > Let it run all night. > > If it's a production server, replace it with one you trust and then > figure out what the problem is with the old box. > > We had 6 app servers at [bloated CA name removed to protect the guilty] > in production and 2 of them were giving us SIG11's. The solution was to > throw them out and replace them with 2 new ones. One of those sucked, > too, so we had to play server-roulette again before we got all 6 good > ones. > > Good luck, > - -chris > > >
We had a similar problem. After running fine for a couple of years, Tomcat on one of our servers started to die every 2 or so hours with the dreaded SIGSEGV (0xb) errors. Since the identical versions of java as well as tomcat were running on our other machines and they had no problems, it would seem to point to a hardware problem on the crashing server. We had our hosting company swap the memory out of that machine and it looks good so far. -- View this message in context: http://www.nabble.com/Fun-with-the-JVM-crashing.-tp21865004p23175427.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
