db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1317) BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?
Date Thu, 11 May 2006 17:39:17 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1317?page=all ]

Mike Matrigali updated DERBY-1317:

It is not really clear this is a bug, unless you are seeing some non standard jdbc behavior.
 I understand it may not be working for your extension, but this is a pretty low level interface.
 Are you seeing any such behavior?

Some description of the driving application may help understand if this is the expected behavior
or not.  
For instance is this an XA transaction.  Or maybe one transaction per connection?  Are these
from real user transactions or maybe internal transactions.

> 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
> 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:
For more information on JIRA, see:

View raw message