db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julius Stroffek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2551) Global Xid value garbled in syscs_diag.transaction_table.
Date Wed, 16 May 2007 22:18:16 GMT

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

Julius Stroffek updated DERBY-2551:

    Attachment: d2551-round2-try2.stat

I changed finally to catch with throwing the same exception further even if another one occurs
(the new one would be ignored since it is not the one that failed the test). Is it ok to do
it that way?I need to call at least rollback on that transaction because the CleanDatabaseSetup
will not be able to clean the database because the transaction will keep holding locks.

> Global Xid value garbled in syscs_diag.transaction_table.
> ---------------------------------------------------------
>                 Key: DERBY-2551
>                 URL: https://issues.apache.org/jira/browse/DERBY-2551
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions:
>            Reporter: Julius Stroffek
>         Assigned To: Julius Stroffek
>             Fix For:,
>         Attachments: d2551-round2-try2.diff, d2551-round2-try2.stat, d2551-round2.diff,
d2551-round2.stat, d2551.diff
> The value of global xid is dumped without leading zeros on GlobalTransactionId and BranchQualifier
byte arrays. Thus, it is impossible to reconstruct the xid value from the transaction_table.

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

View raw message