db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-1317) BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?
Date Mon, 15 Oct 2007 18:56:50 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden resolved DERBY-1317.
-----------------------------------

    Resolution: Invalid

Closing this as invalid as there is no external impact shown.


> BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?
> ------------------------------------------------------------
>
>                 Key: DERBY-1317
>                 URL: https://issues.apache.org/jira/browse/DERBY-1317
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>         Environment: Anyone - the possible bug is in the source code.
>            Reporter: Susana Guedes
>            Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message