Bug 1133346

Summary: XA Recovery scans can stall JBoss startup
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Livingston <jlivings>
Component: Transaction ManagerAssignee: Michael <mmusgrov>
Status: CLOSED CURRENTRELEASE QA Contact: Ondrej Chaloupka <ochaloup>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: hhovsepy, joallen, kkhan, mmusgrov, ochaloup, tom.jenkinson
Target Milestone: DR12   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In JBoss EAP 6, transaction recovery operates by asking resources for their view of in-doubt transaction branches using "RecoveryHelpers" provided by other subsystems. When a deployment registers one of these helpers, a lock is taken. The same lock is acquired when recovering a resource. If the resource is slow to complete a recovery request, then the subsystem deployment (which is waiting for the lock) is similarly delayed. In this release the contention on the lock is broken and subsystems deploy as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1143956    
Bug Blocks:    

Description James Livingston 2014-08-24 22:32:36 UTC
Recovery scans can delay subsystem deployments because of contention on the lock XARecoveryModule._xaResourceRecoveryHelpers. If recovery takes a long time, for example caused by Database performance or connectivity issues, it can stall JBoss startup.

Comment 1 tom.jenkinson 2014-09-02 11:19:03 UTC
fixed in community project, awaiting release

Comment 2 tom.jenkinson 2014-12-05 12:40:35 UTC
Went into 4.17.23

Comment 3 Ondrej Chaloupka 2014-12-10 08:12:54 UTC
Verified. The deployment is not blocked by periodic recovery as described in jira.
This fix is available from DR3.

Comment 4 JBoss JIRA Server 2014-12-11 15:53:59 UTC
Tom Jenkinson <tom.jenkinson@redhat.com> updated the status of jira JBTM-2242 to Closed