When a JAX-WS client is invoked inside an endpoint, the endpoint's MessageContext is bumped out of the ThreadLocal and is not replaced at the end of the client call. This makes the MessageContext unavailable to endpoints after they make any JAX-WS invocation.
Flagged as Known Issue as ticket unresolved at the time of writing the release note.
Solved by update https://bugzilla.redhat.com/show_bug.cgi?id=1087653
Verified on 6.3.0.ER4
I verified that reproducers from customer case test the problem.
I tried to run them with results:
all failed on 6.3.0.ER3
all passed on 6.3.0.ER4
I also checked that fix for CXF-5626 is really included in CXF 2.7.11.