db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julius Stroffek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2953) Dump the information about rollbacks of the global transaction (introduced in DERBY-2220 and DERBY-2432) to derby.log
Date Wed, 25 Jul 2007 08:28:31 GMT

     [ 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.


Mime
View raw message