In debugger i see that inside MVCCHelper.acquireLock:159 invocation context's option
overrides the value of lockAcquisitionTimeout to zero, even though for testing sake i
explicitly set it to non-zero. What is more interesting, is that in the main thread a
second later i can still see my correct non-zero lockAcquisitionTimeout override inside
the context...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266896#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...