may i add, that this is a harmless problem, as tomcat seems to be functioning normally without any errors and no side effects of the shutdown are noticed.... Its only that when u start and stop Tomcat from the command line interface , this message is noticable, so most of us would'nt have even seen this.
if any one has please let me know as soon as possible -ankur -----Original Message----- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 5:29 PM To: 'Tomcat Users List' Subject: RE: problems during shutdown in Tomcat 4.1.18 Did you block port 8005 on your machine? Did you remove the shutdown port definition from server.xml? John > -----Original Message----- > From: Ankur Goel [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 19, 2003 6:28 AM > To: [EMAIL PROTECTED] > Subject: problems during shutdown in Tomcat 4.1.18 > > > hi, > i m new to the user-list. i have a Tomcat 4.1.18 setup > installed and > everything works fine! the problem comes only at shutdown. i get a > > "java.net.bindException: cannot assign the requested address" > > i m giving the complete message log for lookup > > [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/100 config=d:\Tomcat > 4.1.18\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:417) > 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$CatalinaShutdownHook.run( > Catalina.java: > 624) > > what i figured out by looking at the code of > "ChannelSocket.java" was that > in method "init" of class "ChannelSocket" the following code > > if (getAddress() == null) > setAddress("0.0.0.0"); > > is setting 'inet' variable to address 0.0.0.0, which is > creating problems at > the time of shutdown when method "destroy" is called and a new socket > creation is tried which results in the above mentioned "Bind > Exception"... > > if (inet == null) { > s=new Socket("127.0.0.1", port ); > }else{ > s=new Socket(inet, port ); > // setting soLinger to a small value will > help shutdown the > // connection quicker > s.setSoLinger(true, 0); > } > Is this a real bug or there is some other problem which i > don't know??? > (investigating the code does'nt suggest the possibility of > any configuration > problems!!!) > > please help! if any of u knows the problem > > -thanks > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
