Bug 1079043

Summary:	[GSS] (6.3.0) 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 Services	Assignee:	Alessio Soldano <asoldano>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Rostislav Svoboda <rsvoboda>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	jbliznak, kkhan, smumford
Target Milestone:	ER4
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	In previous versions of JBoss EAP 6, when a JAX-WS client was invoked inside an endpoint, the endpoint's MessageContext was 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 addressed in this release of the product.	Story Points:	---
Clone Of:
Clones:	1079044 (view as bug list)		Environment:
Last Closed:	2014-06-28 15:40:32 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:
Bug Blocks:	1079044, 1087653, 1103627

Description Kyle Lape 2014-03-20 20:30:31 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 1 Scott Mumford 2014-04-23 00:16:00 UTC

Flagged as Known Issue as ticket unresolved at the time of writing the release note.

Comment 2 Kabir Khan 2014-04-23 14:01:23 UTC

Solved by update https://bugzilla.redhat.com/show_bug.cgi?id=1087653

Comment 3 Jan Blizňák 2014-05-22 11:51:27 UTC

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.