DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27790>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27790 Exception during shutdown of 5.0.19 on JDK 1.3.1 ------- Additional Comments From [EMAIL PROTECTED] 2004-03-21 21:28 ------- I think I found the problem. One of the recent changes to Http11Protocol.java added pause() and resume() methods which call log.info() to record the actions. However, the corresponding messages were not placed in LocalStrings.properties, so errors occur when attempting to fetch the text. Under JDK 1.4, using the java.util.logging.Logger class, a message is printed, and no exception is thrown for the missing text. However, under 1.3, using the commons SimpleLog class, an exception is thrown, which kills the main thread, resulting in the hang. I've added the following to the properties file: http11protocol.endpoint.pauseerror=Error pausing endpoint http11protocol.pause=Pausing Coyote HTTP/1.1 on port {0} http11protocol.endpoint.resumeerror=Error resuming endpoint http11protocol.resume=Resuming Coyote HTTP/1.1 on port {0} I suspect that there may be other missing message strings, since the LifeCycleException seems to be complaining about a similar problem. This may also explain the recent spate of e-mails on the tomcat-user list about missing messages in the 1.4 log. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
