tomcat 5.5 wants to shut down on its own
When the following exceptions occurs (from the tomcat log, and for which tomcat doesn't include stack traces), tomcat says it's shutting down, although it never does. Any idea: 1) Why these exceptions? 2) Failed to restart: What is it trying to restart? 3) Why tomcat wants to shut down? 4) What to do about them? I don't believe we are throwing these exceptions out to tomcat, as we are catching all Throwables. It is true that we have various hosts around the cluster in the application, which may go up and down. Happens with any version up to 5.5.20. 11:16:54 Info [Tomcat]: Server startup in 50896 ms 13:20:52 Warning [Tomcat]: Failed to restart: java.io.IOException: Failed to get a RMI stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: ; nested exception is: java.net.ConnectException: Connection refused: connect] 13:20:53 Warning [Tomcat]: Failed to call the method close():java.rmi.ConnectException: Connection refused to host: 10.10.101.27; nested exception is: java.net.ConnectException: Connection refused: connect 13:20:53 Warning [Tomcat]: Failed to check connection: java.net.ConnectException: Connection refused: connect 13:20:53 Warning [Tomcat]: stopping tia -- View this message in context: http://www.nabble.com/tomcat-5.5-wants-to-shut-down-on-its-own-tf3371375.html#a9381355 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] tomcat 5.5 wants to shut down on its own
Apparently, these are RMI exceptions from the RMI threads outside the application's control. Does tomcat attempt to shut down on a Warning log message? tk-2506 wrote: > > When the following exceptions occurs (from the tomcat log, and for which > tomcat doesn't include stack > traces), tomcat says it's shutting down, although it never does. Any idea: > 1) Why these exceptions? > 2) Failed to restart: What is it trying to restart? > 3) Why tomcat wants to shut down? > 4) What to do about them? I don't believe we are throwing these exceptions > out to tomcat, as we are > catching all Throwables. > > It is true that we have various hosts around the cluster in the > application, which may go up and down. > Happens with any version up to 5.5.20. > > 11:16:54 Info [Tomcat]: Server startup in 50896 ms > 13:20:52 Warning [Tomcat]: Failed to restart: java.io.IOException: Failed > to get a RMI stub: javax.naming.ServiceUnavailableException [Root > exception is java.rmi.ConnectException: Connection refused to host: ; > nested exception is: > java.net.ConnectException: Connection refused: connect] > 13:20:53 Warning [Tomcat]: Failed to call the method > close():java.rmi.ConnectException: Connection refused to host: > 10.10.101.27; nested exception is: > java.net.ConnectException: Connection refused: connect > 13:20:53 Warning [Tomcat]: Failed to check connection: > java.net.ConnectException: Connection refused: connect > 13:20:53 Warning [Tomcat]: stopping > > tia > > > -- View this message in context: http://www.nabble.com/tomcat-5.5-wants-to-shut-down-on-its-own-tf3371375.html#a9381483 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] tomcat 5.5 wants to shut down on its own
It looks like "stopping" is not written by Tomcat, but by RMI again... case closed. tk-2506 wrote: > > Apparently, these are RMI exceptions from the RMI threads outside the > application's control. > Does tomcat attempt to shut down on a Warning log message? > > > tk-2506 wrote: >> >> When the following exceptions occurs (from the tomcat log, and for which >> tomcat doesn't include stack >> traces), tomcat says it's shutting down, although it never does. Any >> idea: >> 1) Why these exceptions? >> 2) Failed to restart: What is it trying to restart? >> 3) Why tomcat wants to shut down? >> 4) What to do about them? I don't believe we are throwing these >> exceptions out to tomcat, as we are >> catching all Throwables. >> >> It is true that we have various hosts around the cluster in the >> application, which may go up and down. >> Happens with any version up to 5.5.20. >> >> 11:16:54 Info [Tomcat]: Server startup in 50896 ms >> 13:20:52 Warning [Tomcat]: Failed to restart: java.io.IOException: Failed >> to get a RMI stub: javax.naming.ServiceUnavailableException [Root >> exception is java.rmi.ConnectException: Connection refused to host: ; >> nested exception is: >> java.net.ConnectException: Connection refused: connect] >> 13:20:53 Warning [Tomcat]: Failed to call the method >> close():java.rmi.ConnectException: Connection refused to host: >> 10.10.101.27; nested exception is: >> java.net.ConnectException: Connection refused: connect >> 13:20:53 Warning [Tomcat]: Failed to check connection: >> java.net.ConnectException: Connection refused: connect >> 13:20:53 Warning [Tomcat]: stopping >> >> tia >> >> >> > > -- View this message in context: http://www.nabble.com/tomcat-5.5-wants-to-shut-down-on-its-own-tf3371375.html#a9381520 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Downloaded 4.1.36 but says version is 4.1.35?
Downloaded it from http://tomcat.apache.org/download-41.cgi (http://apache.cs.utah.edu/tomcat/tomcat-4/v4.1.36/bin/apache-tomcat-4.1.36.zip) and the version it reports is: Aug 31, 2007 4:29:50 PM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-80 Aug 31, 2007 4:29:50 PM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8090 Starting service Tomcat-Standalone Apache Tomcat/4.1.35 Then I got the sources, and the version is 4.1.35 there too? $ find . -type f | xargs fgrep 4.1.35 ./connectors/build.properties:version=4.1.35 ./container/build.properties:version=4.1.35 ./container/build.properties.default:version=4.1.35 ./container/build.properties~:version=4.1.35 Yet the RELEASE-NOTES-4.1.txt has one entry for 4.1.36: [4.1.36] mx4j Update build process so correct mx4j jar is used Any idea what's going on??? tia -- View this message in context: http://www.nabble.com/Downloaded-4.1.36-but-says-version-is-4.1.35--tf4362429.html#a12433936 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
