https://bz.apache.org/bugzilla/show_bug.cgi?id=59119
Bug ID: 59119
Summary: Improper forced reading causing client read timeout
Product: Tomcat 8
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P2
Component: WebSocket
Assignee: dev@tomcat.apache.org
Reporter: caij...@apache.org
In source code [1], the "forceRead" section (from Line 265 to 273, as of today)
does not reset "forceRead" to false after a forced read. This causes improper
forced reading in follow-up loops even though there are still data in the
socketChannel left over from last unwrap. As a result, it causes timeout in the
WsWebSocketContainer.processResponse() method, and prevents websocket
hand-shaking from completion.
[1]
http://svn.apache.org/repos/asf/tomcat/trunk/java/org/apache/tomcat/websocket/AsyncChannelWrapperSecure.java
--
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
