[jboss-user] [JBossCache] - Re: TreeCache/Hibernate/JBossAS optimistic locking problem

[steve.ebersole@jboss.com]

I have some local mosds to these tests...

I just confirmed with Manik regarding the mixing of calls supplying and calls not supplying a data-version.  Hibernate will need to provided data-version info for all nodes under its control reagrdless of whether optimistically locking these nodes makes any sense...

Reagrding the warning, the message is just a bit misleading (and I have actually changed it locally).  It is really protecting that *inserting* data is not involved in a lock check (because that would mean that data already existed for the entity we are trying to insert).  But I found an interesting thing (which perhaps was the initial thing which caused me to add this): basically, after an insert in one transaction, the node is validated against itself in the next transaction!?!?!  I would guess that it has something to do with the fact that tree cache is registering its synch inthe midst of a beforeCompletion() cycle, but not certain.  Would anything else cause tree cache to validate a non modified node in this manner?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957442#3957442

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957442