Yie
I have solved the problem!!!
Actually I should have used an XADataSource for the underlying database to use
global transactions for the cache.
The clue of the problem was in comments of
TxInterceptor.RemoteSynchronizationHandler.afterCompletion()
-// this
I am using JBossCache 1.3 SP4 with weblogic 8.1 SP4. JBossCache has been
configured to use org.jboss.cache.GenericTransactionManagerLookup - so that the
transaction Manager of weblogic would be used. I am also using a JDBC Cache
Loader configuration
In my code, I have enclosed treeCache.put in
I want to add also that the problem does not occur if I don't use transactions
at all since then records are inserted and committed directly in the database.
However, this is not the preferred solution at all for me!
View the original post :
Thank you so very much for looking into the problem. I was on leave as i had
fallen ill and i just saw your reply. Our isolation level is REPEATABLE_READ
and we are using REPL_SYNC cache mode
Please find below the complete configuration-
?xml version=1.0 encoding=UTF-8?
|
| !--
Thanks a lot, Hany. Yes I seem to have goofed up with the cache configuration.
The real one is below :)). Sorry about that. I will definitely try your
suggestion - this looks to be a very plausible reason for the problem. I will
let you know the result in my next post. In the meantime, just
Hello,
We are using JBoss Cache 1.3 for our project which is under development.
Recently while doing some performance testing we found a problem with the JDBC
Cache Loader (we are using an Oracle database as the backing store for our
JBoss Cache). When we run with multiple threads or
