Bug 1133346 – XA Recovery scans can stall JBoss startup

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

Bug 1133346 - XA Recovery scans can stall JBoss startup

Summary:	XA Recovery scans can stall JBoss startup

Status:	VERIFIED

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Transaction Manager (Show other bugs)
Sub Component:
Version:	6.3.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR12
Target Release:	EAP 6.4.0
Assigned To:	Michael
QA Contact:	Ondrej Chaloupka
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1143956
Blocks:
	Show dependency tree / graph

Reported:	2014-08-24 18:32 EDT by James Livingston
Modified:	2018-03-06 15:39 EST (History)
CC List:	6 users (show)

See Also:
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:	---

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	JBTM-2242	Major	Closed	Misbehaving XAResources may delay deployments	2018-03-20 01:18 EDT
Red Hat Knowledge Base (Solution)	376403	None	None	None	Never

Groups: None (edit)

Description James Livingston 2014-08-24 18:32:36 EDT

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 07:19:03 EDT

fixed in community project, awaiting release

Comment 2 tom.jenkinson 2014-12-05 07:40:35 EST

Went into 4.17.23

Comment 3 Ondrej Chaloupka 2014-12-10 03:12:54 EST

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 10:53:59 EST

Tom Jenkinson <tom.jenkinson@redhat.com> updated the status of jira JBTM-2242 to Closed

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