If the session is invalidated in request 1 while another request 2 still exists in the same session with an associated conversation context, then on the end of the request 2 the conversation context will fail to dissociate and will stick to the thread forever.
The following requests, that happen be served by the affected thread , will get the wrong stuck conversation context associated with them, regardless of propagation rules.
Seems like this problem was encountered in WELD-1607, WFLY-1533, but remained unfixed.
I checked that the issue is present in all specified affected versions and environments.
I was unable to reproduce the issue with Weld 2.2.5.Final on Jetty 9.2.3.
|
