Bug 779699 (SOA-2063) - Backport "JBAS-5880: Synchronization Problem in TxServerClientInterceptor"
Summary: Backport "JBAS-5880: Synchronization Problem in TxServerClientInterceptor"
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2063
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: EAP
Version: 4.3 CP02
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP05
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-30 11:14 UTC by Stelios Koussouris
Modified: 2011-04-21 13:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-21 13:00:22 UTC
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2063 0 Major Closed Backport "JBAS-5880: Synchronization Problem in TxServerClientInterceptor" 2015-11-19 13:02:29 UTC

Description Stelios Koussouris 2010-04-30 11:14:13 UTC 
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=766063&gid=1354
project_key: SOA

Customer Request for inclusion of  Backport JBAS-5880 included in EAP 4.3.0_CP09 into SOA-P 4.3.0
Comment 1 Stelios Koussouris 2010-04-30 11:14:36 UTC 
Link: Added: This issue depends JBPAPP-1119
Comment 2 Stelios Koussouris 2010-04-30 11:16:06 UTC 
Link: Added: This issue incorporates JBAS-5880
Comment 3 Anne-Louise Tangring 2011-02-22 19:32:06 UTC 
This will be resolved when we pick up EAP 4.3 CP09.
Comment 4 nwallace 2011-03-17 14:06:17 UTC 
According to JBPAPP-1119 QE verified this issue was included from EAP 4.3 CP09 CR1. EAP 4.3 CP09
Comment 5 David Le Sage 2011-03-21 01:14:15 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Writer: Added: dlesage
Comment 6 David Le Sage 2011-04-01 05:02:21 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/JBAS-5880

JBoss experienced a synchronization problem when it was started under load. This was because, in the TxServerClientInterceptor  class'  getEmptyPropagationContext method, a static member was initialized without being synchronized. Therefore, a second thread could see the member as being non-null while the first thread was still initialising its data. To fix this issue, a "temp" propagation context, that is only assigned to the member once it is fully initialised, has been constructed. As a result, these synchronisation issues no longer occur.
Comment 7 Jiri Pechanec 2011-04-21 13:00:22 UTC 
Verified in ER2
Note You need to log in before you can comment on or make changes to this bug.