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 Summary: Exception during shutdown of 5.0.19 on JDK 1.3.1 Product: Tomcat 5 Version: 5.0.19 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It appears that a dependency on JDK 1.4 may have crept into the latest Tomcat release build. With 5.0.16, I'm able to shut down Tomcat successfully when it's running on either 1.3 or 1.4; with the 5.0.19 release, shutdown requests on 1.4 operate correctly, but fail with an exception on 1.3: [INFO] Http11Protocol - -http11protocol.pause [ERROR] Catalina - -Catalina.stop <LifecycleException: Cannot find message associated with key coyoteConnector.protocolHandlerPauseFailed>LifecycleException:Cannot find message associated with key coyoteConnector.protocolHandlerPauseFailed at org.apache.coyote.tomcat5.CoyoteConnector.pause (CoyoteConnector.java:1462) at org.apache.catalina.core.StandardService.stop (StandardService.java:560) at org.apache.catalina.core.StandardServer.stop (StandardServer.java:2379) at org.apache.catalina.startup.Catalina.stop(Catalina.java:643) at org.apache.catalina.startup.Catalina.start(Catalina.java:618) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398) The server then hangs, but can be terminated with platform-specific kills. The above came from a Win2K box, but was first observed on a non-Windows platform as well - our mainframe JVM, which is stuck on 1.3 for a while. The real exception has unfortunately been masked by the LifecycleException, since the pause() method caught the original one and threw the Lifecycle error. This is 100% reproducible in a JDK 1.3 environment. Thanks for taking a look. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
