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: Thu, 13 Nov 2008 12:19:42 PST

Hmm... I think that the slide is wrong - it's the T2 that will fail (and the flush() doesn't matter as T1 doesn't see it).

Regards,
-marina
[Message sent by forum member 'mvatkina' (mvatkina)]

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

This message: [ Message body ]
Next message: glassfish_at_javadesktop.org: "Re: And yet another Websphere 5.x to Glassfish App Conversion - JDBC naming"
Previous message: glassfish_at_javadesktop.org: "Re: java.lang.IllegalStateException: Timer already cancelled. - Please help"
In reply to: glassfish_at_javadesktop.org: "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"
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 ]