users@glassfish.java.net
EntityManager's forced version update (lock(WRITE) + flush()) not atomic
This message
: [
Message body
] [ More options (
top
,
bottom
) ]
Related messages
: [
Next message
] [
Previous message
] [
Next in thread
] [
Replies
]
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 00:19:15 PST
Hello,
i was wondering what happens in slide 42 here (
http://developers.sun.com/learning/javaoneonline/2007/pdf/TS-4902.pdf
) if T1's commit() takes place between the lock() and flush() calls of T2.
Both transactions commit succesfully?
[Message sent by forum member 'vladbalan' (vladbalan)]
http://forums.java.net/jive/thread.jspa?messageID=316488
This message
: [
Message body
]
Next message
:
glassfish_at_javadesktop.org: "PHP/Java bridge integration in AMP stack."
Previous message
:
glassfish_at_javadesktop.org: "Deploy MBean to Glassfish"
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"
Maybe reply
:
Mitesh Meswani: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomic"
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]