You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Lin Sun (JIRA)" <ji...@apache.org> on 2009/01/16 23:47:59 UTC
[jira] Resolved: (GERONIMO-4482) a few improvements on XAExceptions
during enlist resource, prepare, commit, rollback
[ https://issues.apache.org/jira/browse/GERONIMO-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun resolved GERONIMO-4482.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.1.4
see subversion commits tab
> a few improvements on XAExceptions during enlist resource, prepare, commit, rollback
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-4482
> URL: https://issues.apache.org/jira/browse/GERONIMO-4482
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: transaction manager
> Affects Versions: 2.1.4, 2.2
> Reporter: Lin Sun
> Assignee: Lin Sun
> Fix For: 2.1.4, 2.2
>
>
> 1. during enlist resource, if there is XAException arisen, we should mark status as rollback only because the enlist resource failed.
> 2. during commit, convert XAER_RMERR, XAER_PROTO & XAER_INVAL to system exceptions.
> 3. if system exceptions arisen during internal prepare, we should roll back the resource(s).
> 4. during rollback, if XA_RBROLLBACK, XAER_RMERR,XAER_NOTA & XAER_RMFAIL arisen, we expect the transaction to be rolled back eventually thus don't throw anything. During commit, we throw rollback exceptions for these.
> 5. if XAER_NOTA arisen from forget, means the resource already forgot the transaction, thus we don't throw any exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.