Bug 1917454

Summary:	[GSS](6.4.z) JBTM-3406 - InboundBridge should recover only local tx / JBTM-3407 - additional logging of XTS SOAP processing
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	Transaction Manager	Assignee:	jboss-set
Status:	CLOSED UPSTREAM	QA Contact:	Pavel Slavicek <pslavice>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.23	CC:	dosoudil, pmackay, thofman, tom.jenkinson
Target Milestone:	CR1
Target Release:	EAP 6.4.24
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 04:00:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1842551, 1871928, 1907942

Description Brad Maxwell 2021-01-18 14:11:37 UTC

InboundBridgeRecoveryManager.checkXid does not correctly check nodename of the xid. Thus where multiple app server nodes share a db, bottom-up recovery can abort branches that don't belong to the node.

We miss more information in server logs for investigation of XTS processing in case of troubles. There should be added more trace logging messages to understand what SOAP messages are processed and what are tasks pushed to TaskManager queue.

Comment 3 Peter Mackay 2022-06-27 17:26:11 UTC

Verified with EAP 6.4.24.CP.CR1

Comment 4 Red Hat Bugzilla 2025-02-10 04:00:29 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.