I've not tried this myself but you could add a Runtime.addShutdownHook and get it to print out anything which will give you a clue.
On Tue, 21 Dec 2004 08:47:49 -0500, Greg Lappen <[EMAIL PROTECTED]> wrote: > Well, turns out the RAM is fine in the server. Our hosting provider > tested it last night and said it checked out fine. Is there any other > reason that the JVM/Tomcat would just exit like this? Could > System.exit() be called somewhere? Isn't there a way to prevent > System.exit() from being called? I know I'm grasping at straws, but > what else is there to do in this situation? > > Greg > On Dec 20, 2004, at 1:57 PM, Eric Rotick wrote: > > > I had a similar problem with an almost identical setup to yours which > > turned out to be bad memory. An extra 1GB stick was added which had a > > bad section in the top of the memory map. This memory only got used > > when things got busy so everyone suspected some threading issue. We > > got lucky and spotted something totally absurd in the logs which > > prompted a memtest86 run and hey presto we got our answer. > > > > > > On Mon, 20 Dec 2004 13:28:56 -0500, Wade Chandler > > <[EMAIL PROTECTED]> wrote: > >> Greg Lappen wrote: > >>> Hello- > >>> > >>> Has anyone had a problem with Tomcat 5.0.28 crashing on Linux with no > >>> error messages? > >>> > >>> My production server running with JDK 1.4.2_06, RedHat EL 3.0 just > >>> crashes, no core dump, no errors in catalina.out, no clues. > >>> Sometimes > >>> it goes for days, sometimes it happens several times in one day. I > >>> am > >>> running the tomcat process behind Apache 2 with mod_proxy. Setting > >>> "ulimit -c unlimited" in the catalina.sh startup file still did not > >>> produce a core file. > >>> > >>> If nobody else has experienced this, do you have any suggestions on > >>> how > >>> to debug it further? > >>> > >>> Thanks, > >>> > >>> Greg > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >> > >> I'm using the same setup as you less Apache2. I use tomcat as the web > >> server. Using TC5.0.28 and JDK1.4.2_06, and I have yet to have the > >> server crash once. Not much help, but might give you some clues where > >> to look. > >> > >> Connector log (mod_proxy....assuming you mean you're using the new > >> connector code)....is there anything in the Apache2 log? I assume > >> from > >> your post you mean that the java process just completely goes away. > >> You > >> might find (depending on the running directory of the java process > >> running tomcat) a pid dump log file or something...not sure if the vm > >> produces one of these or not. You also might check in > >> /var/log/messages > >> file to see if for some reason the kernel or some lib got some error > >> it > >> logged. > >> > >> Wade > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
