]
Frank Hempel commented on WFLY-3109:
------------------------------------
I would just like to confirm this fact. I also see this
"reason-always-null"-behaviour on WildFly 8.0.0.Final as well as the lates
Snapshot (build #1043 (26.03.2014 18:41:28)).
CloseReason always null for WebSocket onClose methods
-----------------------------------------------------
Key: WFLY-3109
URL:
https://issues.jboss.org/browse/WFLY-3109
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 8.0.0.Final
Environment: WildFly 8.0.0.Final on Windows 7 Pro (64 bits) with JDK 7.0u51 (64
bits)
Reporter: Tom Tom
The onClose method of the websocket endpoints does not receive valid CloseReason, it is
always null.
With GlassFish 4.0, the CloseReason is not null and correctly reflects the code and
message used to close the wensocket from the client side.
Simplified code sample of the endpoint:
@ServerEndpoint(value = "/test", configurator = MyConfigurator.class)
public class MyEndpoint {
// onOpen, onMessage and onError, LOGGER are omitted
@OnClose
public void onClose(Session session, CloseReason reason) {
LOGGER.debug("onClose(sessionId={}, reason={})", session.getId(),
reason);
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: