[
https://issues.jboss.org/browse/ISPN-4569?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-4569:
------------------------------------
[~rvansa] we can only add XA resources/synchronizations to the tx on the originator node,
adding resources from another node would be much too complicated. I guess we could always
to the cluster registry modifications from the originator node, but I feel isolating them
in a separated tx should be better.
Inserting into cache with indexing fails for XA transactions
------------------------------------------------------------
Key: ISPN-4569
URL:
https://issues.jboss.org/browse/ISPN-4569
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Embedded Querying, Transactions
Affects Versions: 7.0.0.Alpha5
Reporter: Radim Vansa
Assignee: William Burns
If I setup XA transactions in {{ClusteredQueryDslConditionsTest}} using
{code}
cacheCfg.transaction().transactionMode(TransactionMode.TRANSACTIONAL).useSynchronization(false);
{code}
the test fails. The reason is in deadlock while updating {{ScopedKey}} in
__cluster_registry_cache__ : It seems that on originator we create transaction with
modified inserted key and the {{ScopedKey}} for inserted class, and send it in two prepare
commands to the other node. In the {{ScopedKey}}-prepare, the lock is acquired, but the
regular prepare on the other node does not see it (it is not committed yet) and also tries
to update this {{ScopedKey}} in __cluster_registry_cache__ . This fails with lock
timeout, as the commit is waiting on the regular prepare to finish.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)