Bug 1007005 - Transaction manager UUID generation (getPid) uses synchronized causing contention
Transaction manager UUID generation (getPid) uses synchronized causing conten...
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager (Show other bugs)
All All
unspecified Severity high
: ER2
: EAP 6.2.0
Assigned To: tom.jenkinson
Ondrej Chaloupka
Depends On:
  Show dependency treegraph
Reported: 2013-09-11 13:29 EDT by Andrig T Miller
Modified: 2017-10-09 20:06 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-12-15 11:13:58 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrig T Miller 2013-09-11 13:29:13 EDT
Description of problem:

In profiling SPECjEnterprise2010, we identified an issue in the transaction manager, where there was significant contention.

This was fixed upstream in 5.0, but needs to be backported into 4.17.10.Final.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Use the UUID generation for transaction identification, which I believe is now the default in EAP.

Actual results:

Contention for the start of every transaction.

Expected results:

No contention in starting transactions, improving throughput.

Additional info:

Upstream issue:


Upstream commit:

Comment 1 Andrig T Miller 2013-09-11 13:35:15 EDT
Set the flags for inclusion for EAP 6.2.
Comment 3 tom.jenkinson 2013-09-13 15:53:17 EDT

(getting: For all JBoss bugs, it is mandatory to set the target milestone field to a non-empty value before a bug can be moved past the ASSIGNED state. i.e. to POST, MODIFIED, ON_DEV, ON_QA, VERIFIED or RELEASE_PENDING.)
Comment 6 Ondrej Chaloupka 2013-09-23 03:27:28 EDT
Checked the decopiled code for 6.2.0.ER2.

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