You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Julius Stroffek (JIRA)" <ji...@apache.org> on 2007/07/19 09:15:04 UTC
[jira] Created: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
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
Reporter: Julius Stroffek
Assignee: Julius Stroffek
Fix For: 10.3.1.3, 10.4.0.0
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.
[jira] Updated: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew McIntyre updated DERBY-2953:
-----------------------------------
Fix Version/s: (was: 10.3.1.4)
> 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
> Fix For: 10.4.0.0
>
> 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.
[jira] Updated: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll updated DERBY-2953:
----------------------------------
This issue is targeted for 10.4, but has not been updated in 2008. Should the fix-version be changed/removed?
> 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
> Fix For: 10.4.0.0
>
> 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.
[jira] Updated: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Julius Stroffek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julius Stroffek updated DERBY-2953:
-----------------------------------
Attachment: d2953.stat
d2953.diff
I ran derbyall and suites.All.
In derbyall the wisconsin test failed which is happening also on daily tests.
In suites.All the lang.LangScripts test failed. The same failure occurs to me also on plain trunk. I have posted details to derby-dev.
---
Except the messages being logged I also changed to code in DRDAXAProtocol that it will indirectly use the XATransactionState.cancel method to cancel the transaction. This will lead to the atomic transaction disassociation and rollback being performed in one synchronized block on the corresponding XATransactionState instance.
The best way which I found to do that is to add a method cancelXATransaction to ResourceAdapter which will find the appropriate XATransactionState instance and will call the cancel method. The reference to the ResourceAdapter is kept in drda.XADatabase object instance.
> 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
> Reporter: Julius Stroffek
> Assignee: Julius Stroffek
> Fix For: 10.3.1.3, 10.4.0.0
>
> 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.
[jira] Assigned: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-2953:
-------------------------------------
Assignee: (was: Julius Stroffek)
Unassigning due to inactivity.
> 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
> 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.
[jira] Commented: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Julius Stroffek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julius Stroffek updated DERBY-2953:
-----------------------------------
Derby Info: [Patch Available]
Fix Version/s: (was: 10.3.1.3)
10.3.1.4
> 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
> Reporter: Julius Stroffek
> Assignee: Julius Stroffek
> Fix For: 10.3.1.4, 10.4.0.0
>
> 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.
[jira] Updated: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll updated DERBY-2953:
----------------------------------
Derby Info: (was: [Patch Available])
> 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.
[jira] Commented: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540195 ]
Dyre Tjeldvoll commented on DERBY-2953:
---------------------------------------
Hi Julio,
I could still apply the patch, and both test suites ran successfully for me. Overall the patch looks good. I'm just a bit curious about why some of the new methods have javadoc and some do not. Some have a good description that is not valid javadoc (e.g. without any tags). Was this intentional? I'm never sure when javadoc is required and when it is optional.
> 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
> Fix For: 10.3.1.4, 10.4.0.0
>
> 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.
[jira] Updated: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Julius Stroffek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julius Stroffek updated DERBY-2953:
-----------------------------------
Fix Version/s: (was: 10.4.0.0)
I removed fix-version info.
> 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.
[jira] Commented: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648282#action_12648282 ]
Kathey Marsden commented on DERBY-2953:
---------------------------------------
Julius, Are you still working on this issue? Can you unassign yourself if you are not?
> 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.
[jira] Updated: (DERBY-2953) Dump the information about rollbacks
of the global transaction (introduced in DERBY-2220 and DERBY-2432) to
derby.log
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2953:
----------------------------------
Component/s: JDBC
> 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
> Fix For: 10.3.1.4, 10.4.0.0
>
> 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.