users@glassfish.java.net

Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]

From: <glassfish_at_javadesktop.org>
Date: Wed, 19 Nov 2008 12:08:07 PST

I was wrong :(.

Flush causes an update lock on the row and T1 commit will wait until the lock is released, i.e. until T2 commits.

Sorry about the confusion.
Regards,
-marina
[Message sent by forum member 'mvatkina' (mvatkina)]

http://forums.java.net/jive/thread.jspa?messageID=317690

This message: [ Message body ]
Next message: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi"
Previous message: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomic"
In reply to: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomic"
Next in thread: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi"
Reply: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]