river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Oliver (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-84) Outrigger could resolve transactions atomically
Date Thu, 26 Jul 2007 21:24:03 GMT
Outrigger could resolve transactions atomically
-----------------------------------------------

                 Key: RIVER-84
                 URL: https://issues.apache.org/jira/browse/RIVER-84
             Project: River
          Issue Type: Improvement
          Components: com_sun_jini_outrigger
    Affects Versions: jtsk_1.0
            Reporter: Fred Oliver
            Priority: Trivial


Bugtraq ID [5054755|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5054755]

 Currently if you started with an empty space and you had two clients where :

   Client 1 writes under transaction T entries E1 and E2 that both
   match the template S.

   Client 1 calls commit on T.

   Before the commit on T returns client 2 calls 
      space.take(S, null, 0) and gets E1.

   After the first take returns, but still before
   the commit on T returns client 2 calls 
      space.take(S, null, 0).

Outrigger could return null from the second take. This makes visible that
Outrigger does not atomically commit transactions. I have done a full
investigation, but this would be pretty easy to fix in Outrigger.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message