It basically means the cache will not participate in any transactions that may be running. If you start a tx, do some work including a series of puts/removes on the cache, and then rollback the tx, the following will occur:
1) Each put or remove will immediately be replicated to other nodes in the cluster, rather than being batched and sent as part of the tx commit process.
2) When the tx rolls back, the changes to the cache will not be rolled back.
See http://docs.jboss.org/jbcache/current/TreeCache/html/index.html#d0e205 for more info.
I have the same problem. Not sure why it happens and how I can fix it? I do need transactions!
I define the lookup class in the cache config file as shown below:
Thanks for your help!
<!-- Configure the TransactionManager --> <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
so how do you get hold of a transaction manager out side of jboss.
It can discover a TransactionManager in JNDI bound under the names used by JBoss, Weblogic, JRun, JoOnAS, Resin, Orion, and several versions of Websphere.
i mean is there a way to lookup a transaction manager. Is the Jboss transaction manager available through jndi?
If you are running using JBossAS, yes it is available thru UserTransaction binding.