Just like Martin writes, the following part of your report should be fixed in 2.2.8:
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.
The wrong conversation context should no longer get stuck nor reused by subsequent request. As for the warning we just indicate that the session disappeared while we were touching it.
|