[prev in list] [next in list] [prev in thread] [next in thread] 

List:       slide-dev
Subject:    RE: cvs commit: jakarta-slide/src/share/org/apache/slide/macro Ma
From:       "Pill, Juergen" <Juergen.Pill () softwareag ! com>
Date:       2001-08-30 15:27:16
[Download RAW message or body]

Hi Remy,

If n users try to access an identical document only one user will be
successful, in our implementation the n-1 users are sleeping until either
the resource is free again, or a timeout has occurred.
If the first delete was not successful caused by a time out, he was trying
to delete it again, this time he could be successful. But the enlisted store
had already a backout transaction stored. In this case no exception is send
to the servlet and the commit method is called, which calls prepare and this
method will fail (in AbstractService). The rollbacks are called, but the
commit terminates with an exception.

Best regards,

juergen




 -----Original Message-----
From: 	Remy Maucherat [mailto:remm@apache.org] 
Sent:	Thursday, August 30, 2001 17.10 PM
To:	slide-dev@jakarta.apache.org
Subject:	Re: cvs commit:
jakarta-slide/src/share/org/apache/slide/macro MacroImpl.java

> juergen     01/08/30 07:41:02
>
>   Modified:    src/share/org/apache/slide/macro MacroImpl.java
>   Log:
>   Do not do a second delete. In case of multi user, the second delete may
be successfull and no exception is thrown. Remy, do you want to have a
review on this?

It seems totally ok with me, as I can't remember the purpose of the second
delete.
Why does it succeed the second time in some cases ? (That sounds like a bug
to me)

Remy

[prev in list] [next in list] [prev in thread] [next in thread]