You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/10/17 17:18:30 UTC

DO NOT REPLY [Bug 13736] New: - Socket closed unexpectedly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13736>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13736

Socket closed unexpectedly

           Summary: Socket closed unexpectedly
           Product: Tomcat 4
           Version: 4.1.12
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Connector:Coyote HTTP/1.1
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: kbg@hugvit.is


I am running Tomcat 4.1.12 under Windows NT 4 and using JDK 1.4.0_02.
Every few days I get this error on console:

org.apache.tomcat.util.log.CommonLogHandler log
INFO: Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=80] ignored 
exception: java.net.SocketException: socket closed
java.net.SocketException: socket closed
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:343)
        at java.net.ServerSocket.implAccept(ServerSocket.java:438)
        at java.net.ServerSocket.accept(ServerSocket.java:409)
        at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket
(DefaultServerSocketFactory.java:107)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket
(PoolTcpEndpoint.java:335)
        at org.apache.tomcat.util.net.TcpWorkerThread.runIt
(PoolTcpEndpoint.java:483)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:533)
        at java.lang.Thread.run(Thread.java:536)

It seems that socket for port 80 is closed and the server stops responding, CPU 
usage goes to 100% and this error then repeats forever (for every request), but 
it is not logged to any log file, just to console.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>