[
https://issues.jboss.org/browse/ISPN-3745?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-3745:
-----------------------------------
You're right, as I have synchronous tx cache, the forwarding should be synchronous.
Regrettably, I miss the logs from the forwarding node (it got truncated), just to let you
see what happened:
{code}
04:19:29,410 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher]
(OOB-95,default,apex862-11617) Attempting to execute command: CommitCommand
{gtx=GlobalTransaction:<apex861-22006>:164595:
local, cacheName='testCache', topologyId=18} [sender=apex861-22006]
04:19:29,411 TRACE [org.infinispan.remoting.InboundInvocationHandlerImpl]
(remote-thread-14) Calling perform() on CommitCommand
{gtx=GlobalTransaction:<apex861-22006>:164595:remote, cacheName='testCache',
topologyId=18}
04:19:29,412 TRACE [org.infinispan.remoting.InboundInvocationHandlerImpl]
(remote-thread-14) About to send back response SuccessfulResponse{responseValue=null} for
command CommitCommand {gtx=GlobalTransaction:<apex861-22006>:164595:remote,
cacheName='testCache', topologyId=18}
04:19:31,301 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher]
(OOB-78,default,apex862-11617) Attempting to execute command: PrepareCommand
{modifications=[ ... ], onePhaseCommit=false,
gtx=GlobalTransaction:<apex861-22006>:164595:local, cacheName='testCache',
topologyId=19} [sender=apex863-20495]
{code}
Forwarded Prepare/Commit executed after transaction finished
------------------------------------------------------------
Key: ISPN-3745
URL:
https://issues.jboss.org/browse/ISPN-3745
Project: Infinispan
Issue Type: Bug
Components: Transactions
Affects Versions: 6.0.0.Final
Reporter: Radim Vansa
Assignee: Dan Berindei
Priority: Critical
Labels: 620
Replicated TX cache, nodes A, B, C
0. A and B have topology 2, C already got topology 3
1. A sends prepare with topology 2 to B and C, both apply the prepare and respond
2. C forwards prepare to B with topology 3
3. A sends commit with topology 2 to B and C, both commit and respond
4. again, C forwards prepare to B with topology 3
5. A and B get updated topology id
6. A executes another transaction on the same entry
7. prepare and commit from first transaction with topology 3 arrive at B - B overwrites
(or removes) the entry again
Result: on B we have inconsistent state
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira