db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Susana Guedes (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1317) BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?
Date Thu, 11 May 2006 12:53:08 GMT
BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?
------------------------------------------------------------

         Key: DERBY-1317
         URL: http://issues.apache.org/jira/browse/DERBY-1317
     Project: Derby
        Type: Bug

  Components: JDBC  
 Environment: Anyone - the possible bug is in the source code.
    Reporter: Susana Guedes


Hi everyone,

I am working as a researcher in a European Investigation Project named GORDA - http://gorda.di.uminho.pt/
The goal is to make a patch to Derby to provide in-core replication mechanisms.
Currently i am reflecting the transaction context indicating a transaction Begin / Commit
/ Abort / Close

I think i found a bug in the method destroy() of org.apache.derby.impl.store.raw.xact.Xact
class.

In this method you do:
if(state!=CLOSED){abort();}
close();

I think that you should be doing
if(state!=IDLE){abort();}
close();

Is this really a bug?  In my case the replicator is receiving a lot of ABORT notifications
when he should only be receivig the CLOSE notification.


Regards
Susana 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message