db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2551) Global Xid value garbled in syscs_diag.transaction_table.
Date Thu, 17 May 2007 06:47:16 GMT

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

Knut Anders Hatlen updated DERBY-2551:

    Attachment: j2me.diff

I forgot one thing in the review. I think the test needs to be disabled under J2ME since it
uses XADataSource. The attached patch moves the test into the JDBC 3 section of jdbcapi._Suite
and also makes the test itself check the JDBC version in its suite().
Committed revision 538818.

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