https://bz.apache.org/bugzilla/show_bug.cgi?id=59908
Bug ID: 59908
Summary: Tomcat reports empty(null) close reason if send
operation timed out.
Product: Tomcat 8
Version: 8.0.x-trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: WebSocket
Assignee: [email protected]
Reporter: [email protected]
If Tomcat tryes to send large enough message thought websoket (I've tested
binary messages) not to fit into 20 sec timeout, session is closed with null
reason.
"null" reason goes from
org.apache.tomcat.websocket.FutureToSendHandler.get(long, TimeUnit) method,
which throws "TimeoutException" constructed with default constructor.
Later, in
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.handleSendFailureWithEncode(Throwable)
CloseReason object is created, calling t.getMessage(), which returns null.
The expected behaviour is not to report null close reason, but instead report,
that operation timed out.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
