https://bz.apache.org/bugzilla/show_bug.cgi?id=59710

            Bug ID: 59710
           Summary: java.io.IOException: Connection timed out
           Product: Tomcat 7
           Version: 7.0.69
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebSocket
          Assignee: dev@tomcat.apache.org
          Reporter: hugo.lar...@yahoo.com

Hello, 

We are using Tomcat 7.0.69 and suspect a bug with session.close() when
"Connection timed out" happens sporadically. When the exception is thrown
@onError correctly is called and I call session.close but the connection is
still open in limbo which cause memory leak. 

On the client we use Tyrus with reconnectHandler and set HeartBeatIntervall to
1 minute. When the timeout exception is thrown in Tomcat, Tyrus is still happy
with the connection even though its closed in Tomcat. 

My theory is that there is a problem with session.close() when a timeout
occurs. It never really gets closed. 
I have set the connectionTimeout=-1 connectionUploadTimeout=-1 in server.xml. 

Anyone has a clue? 

BR, 
Hugo 

java.io.IOException: Connection timed out 
        at sun.nio.ch.FileDispatcherImpl.read0(Native Method) 
        at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) 
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) 
        at sun.nio.ch.IOUtil.read(IOUtil.java:192) 
        at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:384) 
        at
org.apache.tomcat.util.net.SecureNioChannel.read(SecureNioChannel.java:442) 
        at
org.apache.coyote.http11.upgrade.NioServletInputStream.fillReadBuffer(NioServletInputStream.java:136)
 
        at
org.apache.coyote.http11.upgrade.NioServletInputStream.doRead(NioServletInputStream.java:80)
 
        at
org.apache.coyote.http11.upgrade.AbstractServletInputStream.read(AbstractServletInputStream.java:129)
 
        at
org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:56)
 
        at
org.apache.tomcat.websocket.server.WsHttpUpgradeHandler$WsReadListener.onDataAvailable(WsHttpUpgradeHa
 
ndler.java:205) 
        at
org.apache.coyote.http11.upgrade.AbstractServletInputStream.onDataAvailable(AbstractServletInputStream
 
.java:203) 
        at
org.apache.coyote.http11.upgrade.AbstractProcessor.upgradeDispatch(AbstractProcessor.java:93)
 
        at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:623)
 
        at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1749)
 
        at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1708)
 
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
        at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
 
        at java.lang.Thread.run(Thread.java:745)

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

Reply via email to