Vsevolod Golovanov Note that the WARN message does not imply the leak (corrupted thread). It's just a warning that there was a problem when dissociating the context - this is expected and unavoidable in similar cases. It would be great if you could test the "stuck conversation" you're describing (this should be fixed in 2.2.8.Final):

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.