[infinispan-issues] [JBoss JIRA] Commented: (ISPN-927) Commits in separate thread to cache operations are not propagated across the cluster in distributed mode

[Sudheer Krishna (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582552#comment-12582552 ] 

Sudheer Krishna commented on ISPN-927:
--------------------------------------

Hi Galder

What you said was true. The commit was happening in a different thread. There is an option given in atomikos to improve the efficiency of commits.

They have an attribute which can set this to false.

http://www.atomikos.com/Documentation/JtaProperties - 

com.atomikos.icatch.threaded_2pc	 Specifies whether or not to use different (and concurrent) threads for two-phase commit on the participating resources. Setting this to true implies that the commit is more efficient since waiting for acknowledgements is done in parallel. Defaults to true. If you set this to false, then commits will happen in the order that resources are accessed within the transaction.



> Commits in separate thread to cache operations are not propagated across the cluster in distributed mode
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-927
>                 URL: https://issues.jboss.org/browse/ISPN-927
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Distributed Cache
>    Affects Versions: 4.2.0.Final, 4.2.1.CR1
>         Environment: Tested in windows
>            Reporter: Sudheer Krishna
>            Assignee: Galder Zamarreño
>             Fix For: 4.2.1.CR2, 4.2.1.Final
>
>         Attachments: cache -framework.rar, testcase.rar, transaction-framework.rar
>
>
> When I try to use transactions and in distributed mode (mode=dist) , changes made inside the transaction in one node is not reflected in the another node. when i change mode to replication everything works fine. So i assume this is a bug with dist mode when transactions is enabled.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira