Hi, We have the following errors during the shutdown Tomcat(using shutdown.bat), It's kind of urgent issue for us, could anyone please help us to find a way to fix it or a workaound? Thanks, li1yang [INFO] Registry - -Loading registry information [INFO] Registry - -Creating new Registry instance [INFO] Registry - -Creating MBeanServer [INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.18 [INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080 [INFO] ChannelSocket - -JK2: ajp13 listening on 0.0.0.0/0.0.0.0:8009 [INFO] JkMain - -Jk running ID=0 time=10/110 config=C:\Program Files\Apache Group\Tomcat 4.1\conf\jk2.properties Stopping service Tomcat-Standalone java.net.BindException: Cannot assign requested address: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124) at java.net.Socket.<init>(Socket.java:268) at java.net.Socket.<init>(Socket.java:122) at org.apache.jk.common.ChannelSocket.destroy(ChannelSocket.java:412) at org.apache.jk.server.JkMain.stop(JkMain.java:308) at org.apache.jk.server.JkCoyoteHandler.destroy (JkCoyoteHandler.java:179) at org.apache.coyote.tomcat4.CoyoteConnector.stop (CoyoteConnector.java:1081) at org.apache.catalina.core.StandardService.stop (StandardService.java:546) at org.apache.catalina.core.StandardServer.stop (StandardServer.java:2224) at org.apache.catalina.startup.Catalina.start(Catalina.java:543) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Post this on tomcat-user (the port is already in use).
There is actually a bug with Tomcat 4.1.x on JDK 1.3 (maybe only on Windows). This is duplicated in Bug 17193 and Bug 17702.
*** This bug has been marked as a duplicate of 17193 ***