[
https://issues.jboss.org/browse/ISPN-927?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-927:
---------------------------------------
@Manik, nope. The IC is looked up from the thread local, not from the transaction table.
And it's the IC that you're interested about cos affectedKeys is a property of IC,
not of the local transaction. If affectedKeys belonged to the local transaction, then
assuming the local transaction was found fine, the code would work. But since it relies on
a thread local, once you switch threads, bye bye affected keys. I should be able to
replicate this issue with any TM if my reasoning is right.
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