Bug 1079043 – [GSS] (6.3.0) MessageContext is lost when JAX-WS client is invoked from within a JAX-WS endpoint impl

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1079043 - [GSS] (6.3.0) MessageContext is lost when JAX-WS client is invoked from within a JAX-WS endpoint impl

Summary:	[GSS] (6.3.0) MessageContext is lost when JAX-WS client is invoked from withi...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Web Services (Show other bugs)
Sub Component:
Version:	6.2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	ER4
Target Release:	EAP 6.3.0
Assigned To:	Alessio Soldano
QA Contact:	Rostislav Svoboda
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1079044 1087653 1103627
	Show dependency tree / graph

Reported:	2014-03-20 16:30 EDT by Kyle Lape
Modified:	2014-07-03 22:38 EDT (History)
CC List:	3 users (show)

See Also:
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 11:40:32 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Apache JIRA	CXF-5626	None	None	None	Never

Groups: None (edit)

Description Kyle Lape 2014-03-20 16:30:31 EDT

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-22 20:16:00 EDT

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

Comment 2 Kabir Khan 2014-04-23 10:01:23 EDT

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

Comment 3 Jan Blizňák 2014-05-22 07:51:27 EDT

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.

Note You need to log in before you can comment on or make changes to this bug.