Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1034650 - Increase the default value of the com.arjuna.ats.jta.orphanSafetyInterval
Increase the default value of the com.arjuna.ats.jta.orphanSafetyInterval
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity high
: ---
: EAP 6.3.0
Assigned To: tom.jenkinson
Ondrej Chaloupka
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-26 04:42 EST by Ondrej Chaloupka
Modified: 2017-10-09 20:20 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
An issue in previous versions of JBoss EAP that could cause numerous rollback XAExceptions to be logged if a transaction's processing time overlaped with the timing of the periodic recovery process's activity has been corrected in this release of the product. The timeout interval of `orphanSafetyInterval` has been increased to 20 seconds which significantly decreases the potential of encountering the exceptions.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-08-06 10:34:25 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)

  None (edit)
Description Ondrej Chaloupka 2013-11-26 04:42:23 EST
As it's described under bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1009981

server log could be filled with rollback XAExceptions when the system is under heavy load. Then there can interleave transaction manager thread and periodic recovery thread.

We agreed that the possibility of getting such exceptions will be decreased by changing (increasing) the default value of the timeout of orphanSafetyInterval. 
The default value for 6.2.0 is 10 seconds. I would like ask to set it to 25 seconds.
Comment 1 tom.jenkinson 2014-03-13 03:39:43 EDT
This went into 4.17.17
Comment 2 Ondrej Chaloupka 2014-05-05 05:23:34 EDT
This was fixed for 6.2.0 release and the default timeout was set to 20 seconds.

There is one more bugzilla opened for 6.3.0 release here:
https://bugzilla.redhat.com/show_bug.cgi?id=1090762
Comment 3 Scott Mumford 2014-06-03 19:42:34 EDT
Drafted release note content and marked for inclusion in 6.3.0 Release Notes.

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