geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Jiang (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-5648) txmanager rollback needs retry scheduler too
Date Tue, 30 Nov 2010 01:11:11 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shawn Jiang resolved GERONIMO-5648.
-----------------------------------

    Resolution: Fixed

the fix was verified in txmanager 2.2.1.

> txmanager rollback needs retry scheduler too
> --------------------------------------------
>
>                 Key: GERONIMO-5648
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5648
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>    Affects Versions: 2.2, 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.2.1, 3.0
>
>         Attachments: GERONIMO-5648-1.patch
>
>
> The following sequence of events can result in a tx branch stuck in a RM until geronimo
is restarted and recovers transactions:
> 1. tx branch prepares
> 2. geronimo decides to rollback the tx
> 3. RM crashes
> 4. attempt to rollback branch fails with e.g. a RETRY error code.
> We can do the same as we do for commits with rollbacks and keep trying until we succeed.
 I think we can also unify the two rollbackResources methods.

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