[jbossts-issues] [JBoss JIRA] Closed: (JBTM-800) Recovery manager not initialised when deploying just the Coordinator

Andrew Dinn (JIRA) jira-events at lists.jboss.org
Fri Oct 15 05:51:40 EDT 2010

     [ https://jira.jboss.org/browse/JBTM-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Dinn closed JBTM-800.

    Fix Version/s: 4.14.0
       Resolution: Done

the (AT and BA) participant and coordinator recovery modules now both create and install a manager if one is not already found. this means the manager is always available even if the host is only configured for one of either coordinator services or participant services.

> Recovery manager not initialised when deploying just the Coordinator
> --------------------------------------------------------------------
>                 Key: JBTM-800
>                 URL: https://jira.jboss.org/browse/JBTM-800
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: XTS
>    Affects Versions: 4.13.0
>            Reporter: Mauro Molinari
>            Assignee: Andrew Dinn
>             Fix For: 4.14.0
> If you deploy just the Coordinator component of XTS and you follow the configuration guidelines, you may be providing just the following recovery manager configuration entries in xts-properties.xml:
> <entry key="org.jboss.jbossts.xts.recovery.coordinatorRecoveryModule1">org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule</entry>
> <entry key="org.jboss.jbossts.xts.recovery.coordinatorRecoveryModule2">org.jboss.jbossts.xts.recovery.coordinator.at.SubordinateATCoordinatorRecoveryModule</entry>
> However, in this way, after the Coordinator has started, you get the following NullPointerException:
> Exception in thread "Periodic Recovery" java.lang.NullPointerException
>  at org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule.processTransactionsStatus(ATCoordinatorRecoveryModule.java:280)
>  at org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule.periodicWorkSecondPass(ATCoordinatorRecoveryModule.java:121)
>  at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789)
>  at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371)
> This is because the recovery manager is currently initialized by the ATParticipantRecoveryModule, which is expected to be made available just on the Participant component.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list