Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <19483300.1179401717445.JavaMail.jira@brutus>
Date: Thu, 17 May 2007 04:35:17 -0700 (PDT)
From: "Julius Stroffek (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2551) Global Xid value garbled in
 syscs_diag.transaction_table.
In-Reply-To: <7839979.1176714375504.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Julius Stroffek commented on DERBY-2551:
----------------------------------------

Thanks, Knut. I did not know that something like your j2me patch is necessary.

Thaks again.

> 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: 10.3.0.0
>            Reporter: Julius Stroffek
>         Assigned To: Julius Stroffek
>             Fix For: 10.2.2.1, 10.3.0.0
>
>         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.