[jbossts-issues] [JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests

Paul Robinson (JIRA) jira-events at lists.jboss.org
Tue Mar 26 13:08:41 EDT 2013

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

Paul Robinson updated JBTM-1522:

     Original Estimate:     (was: 3 days)
    Remaining Estimate:     (was: 3 days)

> "no XTS application recovery module found" during XTS Recovery Tests
> --------------------------------------------------------------------
>                 Key: JBTM-1522
>                 URL: https://issues.jboss.org/browse/JBTM-1522
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Testing, XTS
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.M3
> See:
> Notice the following log is displayed repeatedly until the test gives up waiting for recovery:
> {code}
> WARN  [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0
> {code}
> This error comes from org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple#recoverParticipants(). In particular:
> {code}
>                 if (!found) {
>                     // we failed to find a helper to convert a participant record so log a warning
>                     // but leave it in the table for next time
>                     RecoveryLogger.i18NLogger.warn_participant_at_XTSATRecoveryModule_4(participantRecoveryRecord.getId());
>                 }
> {code}
> It looks like the code is unable to restore the participant from the log due to restoreParticipant(XTSATRecoveryModule module) returning false. There is ParticipantRecoveryRecord in the log as you can see it dumped to the console in the above log. Maybe there is a problem with that log, or maybe we are missing another log?
> This problem is intermittent, so it's unlikely that you will see this happen when you attach a debugger. However, we could attach a debugger to see what happens in the normal case and also to inspect the log to see if anything is missing in the failing case.
> This is the command I run to run just this test:
> {code}
> mvn clean test -Parq -Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit
> {code}
> I've been trying to edit com.arjuna.qa.junit.BaseCrashTest to pass in the debugger arguments, but I can't seem to get it to work. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list