Bug 1079044 - [GSS] (6.2.x) MessageContext is lost when JAX-WS client is invoked from within a JAX-WS endpoint impl
Summary: [GSS] (6.2.x) MessageContext is lost when JAX-WS client is invoked from withi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Services
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.2.4
Assignee: Kyle Lape
QA Contact: Rostislav Svoboda
Russell Dickenson
URL:
Whiteboard:
Depends On: 1079043
Blocks: eap62-cp04-blockers 1069354
TreeView+ depends on / blocked
 
Reported: 2014-03-20 20:32 UTC by Kyle Lape
Modified: 2018-12-05 17:48 UTC (History)
4 users (show)

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).
Clone Of: 1079043
Environment:
Last Closed: 2014-08-07 12:12:46 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA CXF-5626 0 None None None Never

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.
Note You need to log in before you can comment on or make changes to this bug.