Thank you for answer.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263415#4263415
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263415
___
jboss-user mailing list
jboss-use
"bstansbe...@jboss.com" wrote : JBoss Cache doesn't suspend/resume the
transaction; it's Hibernate's integration with JBC that does this. If JBC sees
an active transaction it will hold a lock on data in the cache until that tx
commits. There are times when it's incorrect for those locks to be he
I used JBoss Cache with WebLogic. I noticed that
org.jboss.cache.interceptors.InvocationContextInterceptor suspend/resume xa
transaction. It causes problem on WebLogic when iteration thought ResultSet is
not finished.
I posted it on oracle forum but without any solution
(http://forums.oracle.co
