"nathanmesser" wrote :
| I have a transaction T1, which reads a node A from the cache, so it should
have a read lock on the node.
|
| This transaction is then suspended, when an EJB method is called with it's
transaction attribute set to requiresNew. This transaction T2 then writes to
th
The logs you sent do not show how GlobalTransaction::43 tries to acquire locks
on /Parameters/ISchmParam/4686570, only how to first one succeeds. They seem
incomplete.
Is it possible for you to do the following:
log this : CachePrinter.printCacheLockingInfo(c) immediately after suspending
the
Forgot to mention, the interesting part is the locking of the node
/Parameters/ISchmParam/4686570 in GlobalTransaction::42 and
GlobalTransaction::43
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209645#4209645
Reply to the post :
http://www.jboss.org/inde
Hmm, you will probably want PessimisticNodeBasedLockManager as well.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209545#4209545
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209545
__
I've turned trace logging on for
org.jboss.cache.interceptors.PessimisticLockInterceptor
but all it gave me was the following.
I'm trying to get more comprehensive logs for you, but it's proving difficult
to get the app up with a lot of trace logging turned on.
[ACTIVE] ExecuteThread: '0' for
Have you got PessimisticLockingInterceptor logs to show this behaviour? To
check lock owners, etc. of the data being accessed?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209442#4209442
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=pos
