tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Turner, John" <JTur...@AAS.com>
Subject RE: problems during shutdown in Tomcat 4.1.18
Date Thu, 20 Feb 2003 11:07:34 GMT

No.  I don't use JK2.

John

-----Original Message-----
From: Ankur Goel [mailto:ankur_goel@intersolutions.stpn.soft.net] 
Sent: Thursday, February 20, 2003 6:01 AM
To: tomcat-user@jakarta.apache.org
Subject: problems during shutdown in Tomcat 4.1.18


hi john,
         can u help any further???
-ankur

-----Original Message-----
From: Ankur Goel [mailto:ankur_goel@intersolutions.stpn.soft.net]
Sent: Thursday, February 20, 2003 10:03 AM
To: Tomcat Users List
Subject: RE: problems during shutdown in Tomcat 4.1.18


Is anybody else encountering the same problem during shutdown in Tomcat
4.1.18??? please let me know, 'cause as far as my knowledge goes, the code
of "ChannelSocket.java" of "jk2" looks problematic to me, as shown below...

-ankur

-----Original Message-----
From: Turner, John [mailto:JTurner@AAS.com]
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:ankur_goel@intersolutions.stpn.soft.net]
> Sent: Wednesday, February 19, 2003 6:28 AM
> To: tomcat-user@jakarta.apache.org
> 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: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

---

Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003
 

---

Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003
 

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message