Well, it appears there isn't a problem in this test after all. To answer my own
question above, mvccTCtx gets populated with Node in question in
MVCCNodeHelper.wrapNodeForWriting (called by MVCCLockingInterceptor before
EvictCommand.perform is executed).
Side note: Configuration.writeSkewCheck defaults to false (and not true as specified in
JBC3 User Guide reference section Ch 12, p 104).
So the concurrency problem described in this post is probably rooted elsewhere :-(
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151524&a...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217106#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...