[
https://issues.jboss.org/browse/ISPN-927?page=com.atlassian.jira.plugin.s...
]
Manik Surtani commented on ISPN-927:
------------------------------------
@Galder the InvocationContextContainer should detect that the prepare call thread has a
Transaction context attached to it, and should be able to look up the appropriate
InvocationContext from the TransactionTable. There is no reason why this should not work,
unless the transaction manager doesn't set the Transaction on the preparing thread.
Cache inserts inside a transaction 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
Environment: Tested in windows
Reporter: Sudheer Krishna
Assignee: Galder ZamarreƱo
Fix For: 4.2.1.CR2, 4.2.1.Final, 5.0.0.ALPHA3, 5.0.0.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