[
https://issues.jboss.org/browse/ISPN-927?page=com.atlassian.jira.plugin.s...
]
Sudheer Krishna commented on ISPN-927:
--------------------------------------
The reason I am using static reference is - the transaction lookup class is instantiated
by infinispan.
And my transaction manager is instantiated by spring container. And i wanted to ensure
that spring container instantiates transactionmanager bean before defaultcachemanager()
constructor is called which internally uses the transactionlookup class.
Also I am not using OSGI for hot deployment. I am not using any containers like
tomcat/jboss etc , my code is standalone server.
But I understand your concern with statics in hot/re deployments.
Thanks.
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