Hi, Are you sure this is due to a JDK difference? It looks like a fairly simple message missing from resource bundle type of error. The kind that you'd get if you're mixing 5.0.16 and 5.0.19 jars, as the pause operation is new to this connector in this release.
Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 18, 2004 1:24 PM >To: Tomcat Users List >Subject: Tomcat 5.0.19 shutdown > >It appears that a dependency on JDK 1.4 has 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:14 62) > 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 above came from a Win2K box, but has been observed on non-Windows >platforms as well.) The server then hangs, but can be terminated with >platform-specific kills. > >The real exception has unfortunately been masked by the LifecycleException, >since the pause() method caught the original one and threw the Lifecycle >error. > >Has anybody else seen this? Other than moving to 1.4 (which is not yet an >option on our non-Windows boxes), does anyone have any ideas about how to >get around this? > > - Chuck > > >The company makes me say this: > >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: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
