-
Bug
-
Resolution: Done
-
Major
-
11.0.9.Final, 12.0.1.Final
-
None
-
DataGrid Sprint #57
-
Undefined
In transactional caches, when creating a transaction to put the state, skip enlisting the transaction with the TransactionManager. If we do, the following error may occur:
Caused by: javax.transaction.InvalidTransactionException: WFTXN0002: Transaction is not a supported instance: TransactionImpl{xid=Xid{formatId=2, globalTransactionId=0000000000000001,branchQualifier=0000000000000001}, status=ACTIVE} at org.wildfly.transaction.client@1.1.13.Final//org.wildfly.transaction.client.ContextTransactionManager.resume(ContextTransactionManager.java:148) at org.infinispan@11.0.4.Final//org.infinispan.transaction.impl.TransactionTable.enlist(TransactionTable.java:219)
It happens because we use a custom Transaction implementation to apply the state from the remote node and it can't be handled by the WF TransactionManager.
Note: the server isn't affected because it doesn't have a TransactionSynchronizationRegistry.
- is duplicated by
-
ISPN-12795 Replicated cache with NON_XA transaction fails to syncronize cache data upon Wildfly v.21 (same with v.22) second cluster node start.
- Closed