[
https://issues.apache.org/jira/browse/DERBY-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495517
]
Julius Stroffek commented on DERBY-2551:
----------------------------------------
Thanks, Knut!
1, 3, 4, 6)
Thanks, I'll fix theese.
2.) Using the ClientXid is ok since it only stores the transaction
identification and does not contain any client driver related code. There is no
Xid interface implementation for the embedded driver.
5.) Shouldn't this happen when they got garbage collected? I have consulted the
javadoc for Statement.close and Connection.close methods and prior to version
1.6 they should be closed when they get garbage collected. In version 1.6 this
sentence disappeared. Shouldn't we write the tests more sloppy that also a
garbage collection would be tested?
> 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.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.
