Bug 1079044

Summary: [GSS] (6.2.x) MessageContext is lost when JAX-WS client is invoked from within a JAX-WS endpoint impl
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Kyle Lape <klape>
Component: Web ServicesAssignee: Kyle Lape <klape>
Status: CLOSED CURRENTRELEASE QA Contact: Rostislav Svoboda <rsvoboda>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: bmaxwell, cdewolf, jbliznak, smumford
Target Milestone: CR1   
Target Release: EAP 6.2.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
A bug was present in previous versions of JBoss EAP 6 that, when a JAX-WS client is invoked inside an endpoint, caused the endpoint's MessageContext to be removed from the ThreadLocal and not replaced at the end of the client call. This caused the MessageContext to be unavailable to endpoints after they make any JAX-WS invocation. This bug has been resolved by an upgrade of the Apache CXF component (from 2.7.10 to 2.7.11).
Story Points: ---
Clone Of: 1079043 Environment:
Last Closed: 2014-08-07 12:12:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1079043    
Bug Blocks: 1067534, 1069354    

Description Kyle Lape 2014-03-20 20:32:24 UTC
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.

Comment 3 Rostislav Svoboda 2014-05-07 13:22:29 UTC
CXF was pulled out from CP03. Moving to CP04

Comment 4 Jan Blizňák 2014-06-19 15:50:30 UTC
Verified with 6.2.4.CP.CR1

Reproducers from customer portal case used.