Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: None
Affects Version/s: 1.1.7.Final
Labels:
None

Git Pull Request:
https://github.com/wildfly/wildfly-transaction-client/pull/99, https://github.com/wildfly/wildfly-transaction-client/pull/100

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

During recovery SubordinateXAResource instances are being deserialized and used in the process. XAResourceRegistry associated with given resource is not serialized and resources deserialized by Narayana have no reference to any registry. Lack of interaction with the registry leads to bugs f.e. not removing recovery files from filesystem after successful transaction recovery.

causes

JBEAP-19408 [QE](7.3.z) Unfinished transactions in JMS crash recovery scenario using JTA

Closed

WFLY-12922 server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited

Closed

is incorporated by

JBEAP-18436 (7.3.z) Upgrade wildfly-transaction-client from 1.1.8.Final-redhat-00001 to 1.1.10.Final-redhat-00001

Closed

JBEAP-18437 (7.2.z) Upgrade wildfly-transaction-client from 1.1.8.Final-redhat-00001 to 1.1.9.Final-redhat-00001

Closed

is related to

JBEAP-19435 (7.3.z) WFTC registry records may not be removed during the OpenShift scale down processing when transaction recovery commits

Closed

WFLY-12910 Upgrade wildfly-transaction-client to 1.1.9.Final

Closed

(1 is related to)

Assignee:: Ondrej Chaloupka (Inactive)

Reporter:: Tomasz Adamski

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2019/10/02 7:36 PM

Updated:: 2021/10/24 6:15 AM

Resolved:: 2019/12/19 8:49 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates