Description
When a non persistent connection is closed Undertow will attempt to do a clean close. This can result in the connection close listener being called from the IO thread, which will attempt to end the current exchange. This can result in multiple threads being active in the exchange, which can cause issues such as double freeing of buffers.
Attachments
Issue Links
- clones
-
JBEAP-16046 [GSS](7.2.z) UNDERTOW-1457 - Non persistent connection close may violate Undertow's thread model
- Verified
-
UNDERTOW-1457 Non persistent connection close may violate Undertow's thread model
- Resolved
- incorporates
-
UNDERTOW-1457 Non persistent connection close may violate Undertow's thread model
- Resolved
- is incorporated by
-
JBEAP-16050 [GSS](7.1.z) Upgrade undertow from 1.4.18.SP11 to 1.4.18.SP12
- Resolved