[
https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587938#action_12587938
]
Dyre Tjeldvoll commented on DERBY-2953:
---------------------------------------
Is this issue a true subset of DERBY-2871?
When I apply the patch for this issue and sort out the conflicts, the only
difference I see is that CancelXATransactionTask.run() now catches only
XAExceptions, whereas in DERBY-2871 it catches Throwable. Normally it is not a
good idea to catch Throwable, but I don't know if uncaught exceptions from the
run()-method of a timer gets reported elsewhere... does anyone know?
> Dump the information about rollbacks of the global transaction (introduced in
> DERBY-2220 and DERBY-2432) to derby.log
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2953
> URL: https://issues.apache.org/jira/browse/DERBY-2953
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Reporter: Julius Stroffek
> Assignee: Julius Stroffek
> Attachments: d2953.diff, d2953.stat
>
>
> When the global transaction is going to be rolled back that information
> should be dumped to derby.log so that users can find out what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
