Re: Tomcat dying on its own
Hi everyone, I have the same problem, but a discovered that my problem is generated by logrotate. When logrotate runs, the tomcat pausing, stopping... There is not a tomcat script on the /etc/logrotate.d/ How can I solve that problem? Thanks, Alex Carvalho 2010/12/6 Guillaume Carbonneau guillaume.carbonn...@gmail.com Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat dying on its own
From: Alex Carvalho da Silva [mailto:alexc...@gmail.com] Subject: Re: Tomcat dying on its own How can I solve that problem? First, don't resurrect old threads that were dead and buried months ago. Second, start a new thread for your specific problem, and include pertinent details such as Tomcat version, the origin of your Tomcat download, the JVM level you're running under, and the platform you're running on. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On 08/12/2010 23:23, André Warnier wrote: Mark Thomas wrote: Been there, tried that. There is no easy way (I could find) to distinguish between a legitimate and illegitimate shut-down. Naive suggestion : how about some global flag which the legitimate shutdown paths set (and the others don't know about), and which the hook in question checks ? As I said, been there, tried that. You can log when the shutdown command is used (Tomcat 7 does) but there is no way to distinguish between a kill -15 and code calling system.exit() (unless you run with a security manager as already discussed). Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
I'm late to the party. But how about trying the following ... 1) Add a filter which runs first and logs the request. This WILL have a performance impact - but a non-running application is a tad bit slower than writing each request to disk. With luck - this may call out a class of (or single) urls which can then be examined to see if you can reproduce the app death. 2) Run all the code in the webapp through a decompiler and look for System.exit() - then for all the spots where System.exit exists - then see if that piece of code might be called. [warning: Depending on who wrote the code, or the libraries used - this may violate some licenses.] -Tim On 12/8/2010 5:37 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Victor, On 12/6/2010 3:47 PM, Victor Kabdebon wrote: Your Linux may also be involved. If you have some weird configuration of your system, it may kill/shutdown some services / applications. If it's the Linux OOM killer, you should get a syslog message about it. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
Mark Thomas wrote: On 08/12/2010 23:23, André Warnier wrote: Mark Thomas wrote: Been there, tried that. There is no easy way (I could find) to distinguish between a legitimate and illegitimate shut-down. Naive suggestion : how about some global flag which the legitimate shutdown paths set (and the others don't know about), and which the hook in question checks ? As I said, been there, tried that. You can log when the shutdown command is used (Tomcat 7 does) but there is no way to distinguish between a kill -15 and code calling system.exit() (unless you run with a security manager as already discussed). Maybe what I suggested was misunderstood. The point was not to catch and label the unexpected reasons for stopping. The point was to clearly label the expected and legal ones. E.g. - Tomcat starts. Flag string is set to *unexpected shutdown*. - ... tomcat runs then either a) Tomcat told to shutdown by a legal part of the code. Before that legal part of the code issues the shutdown signal, it resets the flag string to hey, it's me who did that OR b) Tomcat told to shutdown by some application doing a System.exit(). That application does not reset the string, so it remains at *unexpected shutdown*. OR c) Tomcat blown out of the water by a kill -9 to its JVM. No logs, nothing. Then, if the Coyote Connector shutdown code runs, it picks out the value of the flag, and dumps it to the logfile. In case (a), when then have a proper trace in the logs of who decided to shutdown. In the others, we don't, so *we know* that it was not one of the legal ones, and we can tell the OP for sure that it was not Tomcat code who did it. Does that make sense ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On 09/12/2010 12:51, André Warnier wrote: Mark Thomas wrote: On 08/12/2010 23:23, André Warnier wrote: Mark Thomas wrote: Been there, tried that. There is no easy way (I could find) to distinguish between a legitimate and illegitimate shut-down. Naive suggestion : how about some global flag which the legitimate shutdown paths set (and the others don't know about), and which the hook in question checks ? As I said, been there, tried that. You can log when the shutdown command is used (Tomcat 7 does) but there is no way to distinguish between a kill -15 and code calling system.exit() (unless you run with a security manager as already discussed). Maybe what I suggested was misunderstood. The point was not to catch and label the unexpected reasons for stopping. The point was to clearly label the expected and legal ones. E.g. - Tomcat starts. Flag string is set to *unexpected shutdown*. - ... tomcat runs then either a) Tomcat told to shutdown by a legal part of the code. Before that legal part of the code issues the shutdown signal, it resets the flag string to hey, it's me who did that OR b) Tomcat told to shutdown by some application doing a System.exit(). That application does not reset the string, so it remains at *unexpected shutdown*. OR c) Tomcat blown out of the water by a kill -9 to its JVM. No logs, nothing. You are missing d) Something triggers a kill -15 which is a *valid* way to shut down Tomcat if it is user initiated. There is no way to differentiate between b) and d). Further in case d) there is no way to tell if it was initiated by a user (valid) or some unexpected process (invalid). That is the problem here. Tomcat already logs a). It is a given that there is no way to log c). Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Victor, On 12/6/2010 3:47 PM, Victor Kabdebon wrote: Your Linux may also be involved. If you have some weird configuration of your system, it may kill/shutdown some services / applications. If it's the Linux OOM killer, you should get a syslog message about it. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0ACI4ACgkQ9CaO5/Lv0PAAoACfUGhaL6RcYTwuwqwv8SLR47eU cnMAoJlllSFvtHrPUicQVmY/LqH8FXi+ =gAMu -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, On 12/6/2010 3:49 PM, Mark Thomas wrote: On 06/12/2010 20:44, Guillaume Carbonneau wrote: It happens every day or so. Nothing happens before in the log... I'm logging the requests but tomcat dies when there is no traffic it seems. I even tried to bench it with more than 1 requests the other day and it handled the load pretty fine and no crash. I control all the code in my app, there is no System.exit() call There have been cases of libraries calling System.exit() on some error conditions. Isn't there some indication of a System.exit() in catalina.out? If there isn't, we could write an optional Listener that could install a shutdown hook that will complain to stdout if the JVM goes down without Tomcat's permission. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0ACQEACgkQ9CaO5/Lv0PDQ2ACgk8slltfCse1b9Bo5F6m/G/im +mcAnjBW+x3l5MSpOzYOR6Lsy9aluCdL =GbUS -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On 08/12/2010 22:38, Christopher Schultz wrote: Mark, On 12/6/2010 3:49 PM, Mark Thomas wrote: On 06/12/2010 20:44, Guillaume Carbonneau wrote: It happens every day or so. Nothing happens before in the log... I'm logging the requests but tomcat dies when there is no traffic it seems. I even tried to bench it with more than 1 requests the other day and it handled the load pretty fine and no crash. I control all the code in my app, there is no System.exit() call There have been cases of libraries calling System.exit() on some error conditions. Isn't there some indication of a System.exit() in catalina.out? If there isn't, we could write an optional Listener that could install a shutdown hook that will complain to stdout if the JVM goes down without Tomcat's permission. Been there, tried that. There is no easy way (I could find) to distinguish between a legitimate and illegitimate shut-down. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
Mark Thomas wrote: On 08/12/2010 22:38, Christopher Schultz wrote: Mark, On 12/6/2010 3:49 PM, Mark Thomas wrote: On 06/12/2010 20:44, Guillaume Carbonneau wrote: It happens every day or so. Nothing happens before in the log... I'm logging the requests but tomcat dies when there is no traffic it seems. I even tried to bench it with more than 1 requests the other day and it handled the load pretty fine and no crash. I control all the code in my app, there is no System.exit() call There have been cases of libraries calling System.exit() on some error conditions. Isn't there some indication of a System.exit() in catalina.out? If there isn't, we could write an optional Listener that could install a shutdown hook that will complain to stdout if the JVM goes down without Tomcat's permission. Been there, tried that. There is no easy way (I could find) to distinguish between a legitimate and illegitimate shut-down. Naive suggestion : how about some global flag which the legitimate shutdown paths set (and the others don't know about), and which the hook in question checks ? Other naive suggestion/question : something somewhere already intercepts a System.exit(), if i judge by the shutdown messages of the Connectors. How about making the flag a code or string, which would indicate which legitimate agent triggered it, and which the things which print the Connector shutdown messages obtain and duly add to their shutdown message ? The absence of ditto (or the initialisation content of it) would be a telltale sign. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On 06.12.2010 23:36, Guillaume Carbonneau wrote: On Mon, Dec 6, 2010 at 2:25 PM, Konstantin Kolinko knst.koli...@gmail.com wrote: 2010/12/6 Guillaume Carbonneauguillaume.carbonn...@gmail.com: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... At least, it is not a sudden death. Tomcat can be shut down by sending a certain string to port 8005 on localhost (see the first lines of server.xml), - normal shutdown or by sending a system signal that causes JVM to exit, or by calling System.exit(). - shutdown hook perform the shutdown You can install a Listener and print a stacktrace when the stop event happens. The stack traces for the normal shutdown sequence and for the shutdown hook will be different. The Linux out-of-memory killer was already mentioned. BTW, you are not alone: such a thread happens here every 4-6 months. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org I seem to have solved the problem at least temporarily through this solution : I installed the latest JDK on the deployed machine and ran tomcat through catalina.sh debug, then run No crash so far so good. When starting Tomcat interactively you should be aware that some shells kill all child processes when you log out (or get logged out automatically). There's nohup though. I'm not sure what kind of signal is used then, so I can't tell whether the orderly shutdown messages in your logs contradict that theory or not. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
Op dinsdag, 7 december 2010 09:52 schreef Rainer Jung rainer.j...@kippdata.de: On 06.12.2010 23:36, Guillaume Carbonneau wrote: On Mon, Dec 6, 2010 at 2:25 PM, Konstantin Kolinko knst.koli...@gmail.com wrote: 2010/12/6 Guillaume Carbonneauguillaume.carbonn...@gmail.com: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... At least, it is not a sudden death. Tomcat can be shut down by sending a certain string to port 8005 on localhost (see the first lines of server.xml), - normal shutdown or by sending a system signal that causes JVM to exit, or by calling System.exit(). - shutdown hook perform the shutdown You can install a Listener and print a stacktrace when the stop event happens. The stack traces for the normal shutdown sequence and for the shutdown hook will be different. The Linux out-of-memory killer was already mentioned. BTW, you are not alone: such a thread happens here every 4-6 months. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org I seem to have solved the problem at least temporarily through this solution : I installed the latest JDK on the deployed machine and ran tomcat through catalina.sh debug, then run No crash so far so good. When starting Tomcat interactively you should be aware that some shells kill all child processes when you log out (or get logged out automatically). There's nohup though. I'm not sure what kind of signal is used then, so I can't tell whether the orderly shutdown messages in your logs contradict that theory or not. Regards, Rainer Nohup stands for 'no hup', so the signal is HUP and that means HANG-UP as in disconnect your modem. Only the modem is replaced with ssh nowadays. Ronald.
Re: Tomcat dying on its own
On 07.12.2010 12:27, Ronald Klop wrote: Op dinsdag, 7 december 2010 09:52 schreef Rainer Jung rainer.j...@kippdata.de: On 06.12.2010 23:36, Guillaume Carbonneau wrote: When starting Tomcat interactively you should be aware that some shells kill all child processes when you log out (or get logged out automatically). There's nohup though. I'm not sure what kind of signal is used then, so I can't tell whether the orderly shutdown messages in your logs contradict that theory or not. Nohup stands for 'no hup', so the signal is HUP and that means HANG-UP as in disconnect your modem. Only the modem is replaced with ssh nowadays. Of course. Think before write. And yes, the HUP signal calls the shutdown hook of the JVM, so Tomcat will shut down orderly when receiving HUP. Result: it could also have been logout or auto-logout from the shell. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On Tue, Dec 7, 2010 at 12:52 AM, Rainer Jung rainer.j...@kippdata.de wrote: On 06.12.2010 23:36, Guillaume Carbonneau wrote: On Mon, Dec 6, 2010 at 2:25 PM, Konstantin Kolinko knst.koli...@gmail.com wrote: 2010/12/6 Guillaume Carbonneauguillaume.carbonn...@gmail.com: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... At least, it is not a sudden death. Tomcat can be shut down by sending a certain string to port 8005 on localhost (see the first lines of server.xml), - normal shutdown or by sending a system signal that causes JVM to exit, or by calling System.exit(). - shutdown hook perform the shutdown You can install a Listener and print a stacktrace when the stop event happens. The stack traces for the normal shutdown sequence and for the shutdown hook will be different. The Linux out-of-memory killer was already mentioned. BTW, you are not alone: such a thread happens here every 4-6 months. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org I seem to have solved the problem at least temporarily through this solution : I installed the latest JDK on the deployed machine and ran tomcat through catalina.sh debug, then run No crash so far so good. When starting Tomcat interactively you should be aware that some shells kill all child processes when you log out (or get logged out automatically). There's nohup though. I'm not sure what kind of signal is used then, so I can't tell whether the orderly shutdown messages in your logs contradict that theory or not. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Thanks for the advice. I started it in a screen tho so it should be fine. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat dying on its own
Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On 12/6/10 7:45 PM, Guillaume Carbonneau wrote: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... How often does this happen? What happens before that in the logs? If you have an access log configured, what requests occur shortly before until that time? Do you control all of the source code in your application, and if so is there a System.exit() call in your code? p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
RE: Tomcat dying on its own
From: Guillaume Carbonneau [mailto:guillaume.carbonn...@gmail.com] Subject: Tomcat dying on its own My tomcat server seems to die on its own without leaving any backtrace... Suggest you remove the System.exit() call that's in one of your webapps... In all seriousness, that is the most likely culprit. You can enable a SecurityManager to prevent such silliness (although that may prove to be a non-trivial exercise). - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guillaume, On 12/6/2010 2:45 PM, Guillaume Carbonneau wrote: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 So, was there anything in catalina.out just prior to those messages? How about any other log files from the server? localhost.out? Anything else? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkz9Q4kACgkQ9CaO5/Lv0PCgygCgkgmglzPLnUqo5UQqL4kqORB4 //QAn2L7RHOro88rB/1FPntp0W1dlt3w =7KNP -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On Mon, Dec 6, 2010 at 11:54 AM, Pid p...@pidster.com wrote: On 12/6/10 7:45 PM, Guillaume Carbonneau wrote: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... How often does this happen? What happens before that in the logs? If you have an access log configured, what requests occur shortly before until that time? Do you control all of the source code in your application, and if so is there a System.exit() call in your code? p It happens every day or so. Nothing happens before in the log... I'm logging the requests but tomcat dies when there is no traffic it seems. I even tried to bench it with more than 1 requests the other day and it handled the load pretty fine and no crash. I control all the code in my app, there is no System.exit() call - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
Your Linux may also be involved. If you have some weird configuration of your system, it may kill/shutdown some services / applications. But this is really puzzling Victor Kabdebon http://www.voxnucleus.fr 2010/12/6 Guillaume Carbonneau guillaume.carbonn...@gmail.com On Mon, Dec 6, 2010 at 11:54 AM, Pid p...@pidster.com wrote: On 12/6/10 7:45 PM, Guillaume Carbonneau wrote: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... How often does this happen? What happens before that in the logs? If you have an access log configured, what requests occur shortly before until that time? Do you control all of the source code in your application, and if so is there a System.exit() call in your code? p It happens every day or so. Nothing happens before in the log... I'm logging the requests but tomcat dies when there is no traffic it seems. I even tried to bench it with more than 1 requests the other day and it handled the load pretty fine and no crash. I control all the code in my app, there is no System.exit() call - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On 06/12/2010 20:44, Guillaume Carbonneau wrote: It happens every day or so. Nothing happens before in the log... I'm logging the requests but tomcat dies when there is no traffic it seems. I even tried to bench it with more than 1 requests the other day and it handled the load pretty fine and no crash. I control all the code in my app, there is no System.exit() call There have been cases of libraries calling System.exit() on some error conditions. Also check /vat/log/syslog for the Linux out of memory killer. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
i'm monitoring the process today (sending the same query every 5 seconds). it crashed twice. i'm trying to figure out the pattern. somehow I don't think it has to do with the number of requests On Mon, Dec 6, 2010 at 12:49 PM, Mark Thomas ma...@apache.org wrote: On 06/12/2010 20:44, Guillaume Carbonneau wrote: It happens every day or so. Nothing happens before in the log... I'm logging the requests but tomcat dies when there is no traffic it seems. I even tried to bench it with more than 1 requests the other day and it handled the load pretty fine and no crash. I control all the code in my app, there is no System.exit() call There have been cases of libraries calling System.exit() on some error conditions. Also check /vat/log/syslog for the Linux out of memory killer. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
2010/12/6 Guillaume Carbonneau guillaume.carbonn...@gmail.com: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... At least, it is not a sudden death. Tomcat can be shut down by sending a certain string to port 8005 on localhost (see the first lines of server.xml), - normal shutdown or by sending a system signal that causes JVM to exit, or by calling System.exit(). - shutdown hook perform the shutdown You can install a Listener and print a stacktrace when the stop event happens. The stack traces for the normal shutdown sequence and for the shutdown hook will be different. The Linux out-of-memory killer was already mentioned. BTW, you are not alone: such a thread happens here every 4-6 months. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat dying on its own
On Mon, Dec 6, 2010 at 2:25 PM, Konstantin Kolinko knst.koli...@gmail.com wrote: 2010/12/6 Guillaume Carbonneau guillaume.carbonn...@gmail.com: Hi everyone, My tomcat server seems to die on its own without leaving any backtrace... The last info I get in the logs are : Dec 3, 2010 6:11:35 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8077 Dec 3, 2010 6:11:36 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Dec 3, 2010 6:11:36 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8077 Running The Apache Tomcat 6.0 (6.0.29) Linux Oracle Red hat : 2.6.18-194.el5 java version 1.6.0_21 This has happened more than once and will occur even if there is no traffic. restarting brings it back up but it has proven to be unreliable... At least, it is not a sudden death. Tomcat can be shut down by sending a certain string to port 8005 on localhost (see the first lines of server.xml), - normal shutdown or by sending a system signal that causes JVM to exit, or by calling System.exit(). - shutdown hook perform the shutdown You can install a Listener and print a stacktrace when the stop event happens. The stack traces for the normal shutdown sequence and for the shutdown hook will be different. The Linux out-of-memory killer was already mentioned. BTW, you are not alone: such a thread happens here every 4-6 months. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org I seem to have solved the problem at least temporarily through this solution : I installed the latest JDK on the deployed machine and ran tomcat through catalina.sh debug, then run No crash so far so good. I might try tomcat 7 later too to see if it solves the issue Thanks for all the tips everyone - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
