tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41530] New: - stopping a connector produces intermittent SocketException
Date Fri, 02 Feb 2007 19:22:55 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41530>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41530

           Summary: stopping a connector produces intermittent
                    SocketException
           Product: Tomcat 6
           Version: 6.0.7
          Platform: All
        OS/Version: Mac OS X 10.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: paulmcmahan@gmail.com


Geronimo embeds tomcat by wrappering org.apache.catalina.startup.Embedded as a
gbean.  Geronimo stops an http connector by calling the stop() method of
org.apache.catalina.connector.Connector.  Depending on the current state of the
connector when it is stopped, the socket connected to it can throw the following
exception:

Feb 2, 2007 2:20:05 PM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
SEVERE: Socket accept failed
java.net.SocketException: Socket closed
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
        at java.net.ServerSocket.implAccept(ServerSocket.java:450)
        at java.net.ServerSocket.accept(ServerSocket.java:421)
        at
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61)
        at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:310)
        at java.lang.Thread.run(Thread.java:613)

This behavior is intermittent but occurs frequently in the unit test cases for
Geronimo's tomcat gbean and when the Geronimo server is shut down.

The exception occurs when the socket opened by JIoEndpoint.Acceptor.run() is
closed by JIoEndpoint.unlockAccept().  In that case it seems that the
SocketException should be ignored.  Checking to see if the JIoEndpoint is
actually running before logging the error is one way to avoid this problem.  I
will attach a patch for that approach shortly.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message