LRA functionality is implemented using JAX-RS server request and response filters. The inbound filter creates an LRA context, storing it in a ThreadLocal. The expectation is that the filtered method runs with the same thread used for executing the filter, however, the JAX-RS specification does not require that that the filter and target resource method run with the same thread. When the TCK is ran using WildFly we are seeing occasional failures due to this assumption because unrelated tests are picking up the same context.

The fix is to use resteasy header context propagation. Although such functionality exists in MP Context Propagation it does not exist in any of the released libraries that we are using. I am discussing the problem with the RestEasy team.