You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Susana Guedes (JIRA)" <de...@db.apache.org> on 2006/05/11 14:53:08 UTC

[jira] Created: (DERBY-1317) BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?

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


[jira] Updated: (DERBY-1317) BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?

Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
     [ 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 notifications
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 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


[jira] Updated: (DERBY-1317) BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?

Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1317?page=all ]

Daniel John Debrunner updated DERBY-1317:
-----------------------------------------

    Priority: Minor  (was: Major)

No external impact

> 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
>          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.
-
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

        

[jira] Updated: (DERBY-1317) BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?

Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1317?page=all ]

Mike Matrigali updated DERBY-1317:
----------------------------------

    Component: Store
                   (was: JDBC)

changed to store as that is where the routine being described is located.  

> 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: Store
>  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


[jira] Resolved: (DERBY-1317) BUG IN org.apache.derby.impl.store.raw.xact.Xact.destroy() ?

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ 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.