geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2838) Fix Transaction Recovery bug
Date Thu, 08 Mar 2007 00:41:24 GMT

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

Kevan Miller closed GERONIMO-2838.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.2)
                       (was: 2.0)
                   2.0-beta1

Transaction Recovery is looking much better. Basic flows seem to be working, correctly. If
any other problems pop up, we can fix in other Jiras.

Multiple problems were fixed. First, XAResources were not being identified as recoverable
resources. Next, database configuration was occurring too late during server startup. So,
DB creation and/or access was not working properly. Next, ActivationSpecs were not being properly
added to the ResourceManagers ReferenceCollection. So, MDB's would never be recovered... 

> Fix Transaction Recovery bug
> ----------------------------
>
>                 Key: GERONIMO-2838
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2838
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: connector
>    Affects Versions: 1.1.1, 1.2, 2.0
>            Reporter: Kevan Miller
>         Assigned To: Kevan Miller
>            Priority: Critical
>             Fix For: 2.0-beta1
>
>
> On server restart, Geronimo is not cleaning up in doubt transactions. 
> Problem is that ManagedConnectionInfo's are not being properly initialized -- they don't
realize they have XA Resources.

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