-
Bug
-
Resolution: Done
-
Major
-
None
-
None
We found an example of registering a close listener in addition to a "receive" listener: https://github.com/7erry/hazelcast-websocket-demo/blob/master/hazelcast-undertow/src/main/java/demo/hazelcast/undertow/ConnectionCallback.java#L46-L53
This "close" listener is called at the right time, but we didn't expect to need a separate listener than our onClose/onError, given that a "clean" closure is received normally by listener.onClose.
We found two wrappers in the wild that don't register a close listener and are subject to the same issue:
- https://github.com/jooby-project/jooby/blob/f32a916e98d2155acf4a8395c688e91105f455c6/modules/jooby-utow/src/main/java/io/jooby/internal/utow/UtowWebSocket.java#L165-L166
- https://github.com/luminus-framework/ring-undertow-adapter/blob/master/src/ring/adapter/undertow/websocket.clj#L73
Please let us know if we're missing something, or if there's anything we can provide to help diagnose.
- is incorporated by
-
WFCORE-6057 Upgrade Undertow to 2.3.0.Final (CVE-2022-2764)
- Closed
-
WFLY-17017 Upgrade Undertow to 2.3.0.Beta1
- Closed
-
WFCORE-6056 Upgrade Undertow to 2.3.0.Beta1
- Closed
- is related to
-
UNDERTOW-2059 Check reversed scenario to test present in UNDERTOW-1934
- Open