Re: Tomcat/JVM crashes on Linux
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_proxyassuming 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]
Re: Tomcat/JVM crashes on Linux
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_proxyassuming 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]
Re: Tomcat/JVM crashes on Linux
That's a good idea, I'm going to try that. Its a cheap way to confirm or deny my suspicions. Thanks! On Dec 21, 2004, at 9:20 AM, Eric Rotick wrote: 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_proxyassuming 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat/JVM crashes on Linux
I'd be interested to know the outcome of this one when you crack it. On Tue, 21 Dec 2004 09:32:42 -0500, Greg Lappen [EMAIL PROTECTED] wrote: That's a good idea, I'm going to try that. Its a cheap way to confirm or deny my suspicions. Thanks! On Dec 21, 2004, at 9:20 AM, Eric Rotick wrote: 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_proxyassuming 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] - 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]
Re: Tomcat/JVM crashes on Linux
Greg Lappen wrote: That's a good idea, I'm going to try that. Its a cheap way to confirm or deny my suspicions. Thanks! On Dec 21, 2004, at 9:20 AM, Eric Rotick wrote: 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_proxyassuming 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Yoav would be able to answer this much better than I, but you should be able to modify the security settings of Tomcat to not allow that call from any of the web apps. I think tomcat has it's own policy file, and you can also add your own policies to only allow the call from certain code bases. In the java docs for the jdk 1.4.x look up Policy file and from there you'll find all kinds of information on permissions and code security. You can limit only certain jar files specifically to be able to call this method. Which Tomcat 5.0.x might already do thisI haven't actually tried to tell you the truth. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat/JVM crashes on Linux
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]
Re: Tomcat/JVM crashes on Linux
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_proxyassuming 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]
Re: Tomcat/JVM crashes on Linux
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_proxyassuming 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]
Re: Tomcat/JVM crashes on Linux
When you say the problem was similar, did you also have no core dump or log messages, just a missing JVM process? I am asking our hosting provider to test the server's RAM - I was going to do this before but since no other process ever crashes (Apache, MySql, etc.) we didn't think it could be the RAM. 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_proxyassuming 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]
Re: Tomcat/JVM crashes on Linux
What kind of load does your application handle? I am not processing a HUGE amount of requests, but we server about 6000 visitors a day, 15,000 pages. Greg On Dec 20, 2004, at 1:28 PM, Wade Chandler 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_proxyassuming 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]
Re: Tomcat/JVM crashes on Linux
Greg Lappen wrote: What kind of load does your application handle? I am not processing a HUGE amount of requests, but we server about 6000 visitors a day, 15,000 pages. Greg On Dec 20, 2004, at 1:28 PM, Wade Chandler 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_proxyassuming 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] No where that load on the system I wrote about though it stays up and I haven't rebooted the system or restarted the process in a good number of days. It's only in the hundreds a day. I have another application which runs over http using rpc with serialized classes, and it processes quite a bit of information, plus it spawns it's own threads. It uses apache and/or iis as the front end. Though if it were up to me we would only be using tomcat. We were using an ISAPI c++ application for everything at one time. We are adding more and more functionality to it. I'm sure it uses more process and memory resources as it will run backend import processes, a ton of logic processing, and report generation, and the pure nature of the application will have more hits a day with more fire power per hit than your web site. In testing it hasn't crashed. What are your memeory settings for your tomcat process? If you don't give the process enough memory to do what it has to do it won't be able to behave correctly. Though catalina.out should show you out of memory errors like that. Have you used any testing environment to profile the system and gathered any information about the state of the machine when it will crash? Have you been able to reproduce the issue with any valid results yet? I'd be asking myself how best to do this. You can write a simple application to test your web application, or you could purchase some software to hit a bunch of web pages. Basically you can spawn a bunch of threads from a given machine randomly hitting different links and try to reproduce the issue if you don't have any real hard logic there to test. Do you have any application logic in your site? If so, do you perform any logging or anything of that nature? You may be getting some exception you could have caught and logged yourself like an out of memory error before tomcat barfed out. Something obviously has to be happening for the process to just go away. Do you have to use Apache2 as a front end to the application? If not see if you are able to produce the same issue using only tomcat. Be sure you edit your memory settings for tomcat. Don't try to run it in 128MB of memory or something like that. ulimit is fine as far as linux goes, but you still need to be sure and not have any limits on the JVM. For instance, the default value for -Xmx is 64 which means 64 mega bytes. Depending on how much memory you have on your computer you probably want to up this (orin your case you definitely want to up this). With that many hits you may very well be getting enough hits at the same time during the busy moments of the day to crash you out as I'm not sure how tomcat will behave if it is hammered and doesn't have any room to play. You can add something like (granted you aren't already using -Xmx) JAVA_OPTS=$JAVA_OPTS -Xmx1000m to your catalina.sh file so that you can give
Re: Tomcat/JVM crashes on Linux
No core dump and nothing significant in the log files. The process just went away. Actually now I think about it we did have some other weirdness like JARs that were corrupt that also went away with the good memory. On Mon, 20 Dec 2004 15:13:35 -0500, Greg Lappen [EMAIL PROTECTED] wrote: When you say the problem was similar, did you also have no core dump or log messages, just a missing JVM process? I am asking our hosting provider to test the server's RAM - I was going to do this before but since no other process ever crashes (Apache, MySql, etc.) we didn't think it could be the RAM. 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_proxyassuming 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]
Re: Tomcat/JVM crashes on Linux
The application receives data packets from acoustic sensors. While the total load is not huge, because of the way the data is collected there are periods of no activity and then periods when all hell breaks loose. This happens every 15 minutes and we size the memory based on the use of swap over a 24 hour period. Tomcat is by far this biggest process and it can grow quite large due to internal queuing waiting for other services to become available. On average there are 2,500 hits every 15 minutes spread across 2 machines in a cluster. On Mon, 20 Dec 2004 15:15:17 -0500, Greg Lappen [EMAIL PROTECTED] wrote: What kind of load does your application handle? I am not processing a HUGE amount of requests, but we server about 6000 visitors a day, 15,000 pages. Greg On Dec 20, 2004, at 1:28 PM, Wade Chandler 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_proxyassuming 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]
