[JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1522:
--------------------------------
Description:
See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
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 entry?
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. But I have a cunning plan...
h4.Cunning Plan
We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take:
# Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Make sure you create the folder structure under target/surefire-reports so that CI archives it off. Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it.
# Update the "narayana-JBTM-1522" job in CI to use your branch, containing the change above.
# Configure the job to run @hourly until it fails with this problem.
# Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build.
# Boot the AS and confirm that the issue is reproduced.
# You can now keep putting the tx-object-store back in place every time you need to reproduce the issue.
# Attach a debugger to find out what the problem is.
was:
See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
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 entry?
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. But I have a cunning plan...
h4.Cunning Plan
We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take:
# Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it.
# Create a job in CI that runs just the recovery tests using your branch, containing the change above.
# Run regularly until it fails with this problem.
# Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build.
# Boot the AS and confirm that the issue is reproduced.
# You can now keep putting the tx-object-store back in place every time you need to reproduce the issue.
# Attach a debugger to find out what the problem is.
> "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: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
> 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 entry?
> 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. But I have a cunning plan...
> h4.Cunning Plan
> We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take:
> # Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Make sure you create the folder structure under target/surefire-reports so that CI archives it off. Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it.
> # Update the "narayana-JBTM-1522" job in CI to use your branch, containing the change above.
> # Configure the job to run @hourly until it fails with this problem.
> # Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build.
> # Boot the AS and confirm that the issue is reproduced.
> # You can now keep putting the tx-object-store back in place every time you need to reproduce the issue.
> # Attach a debugger to find out what the problem is.
--
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
11 years, 10 months
[JBoss JIRA] (JBTM-1572) a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1572?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-1572:
----------------------------------------
I think it only works on a clean checkout and thereafter fails every time. In addition, once failed it pops up a dialog box and no more jobs can run in that workspace until such time that a hudson user logs in and clicks the OK button.
I guess what I am saying is there is only negative value in setting up a repeating job for this issue. A better solution would be to run it as a linux quickstart since we know that works and we get exposure when anything is committed that might break the quickstart. For example, I am concerned that we haven't tested database access functionality with the new transaction transport.
> a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't
> ------------------------------------------------------------------------------------------------
>
> Key: JBTM-1572
> URL: https://issues.jboss.org/browse/JBTM-1572
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Fix For: 5.0.0.Final
>
> Attachments: client.valgrind, server.valgrind, windbg.out
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Note, it will definitely be worth doing this in a branch/pull as I suspect the database isn't running atm so that will need a kick too
--
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
11 years, 10 months
[JBoss JIRA] (JBTM-1359) Proxy Recovery Manager
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1359?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1359:
--------------------------------
Description: JTA should work, but must consider JTS and XTS too (encoded IP addresses in log records)
> Proxy Recovery Manager
> ----------------------
>
> Key: JBTM-1359
> URL: https://issues.jboss.org/browse/JBTM-1359
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTA, JTS, Recovery, XTS
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M3
>
> Original Estimate: 3 weeks
> Remaining Estimate: 3 weeks
>
> JTA should work, but must consider JTS and XTS too (encoded IP addresses in log records)
--
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
11 years, 10 months
[JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1522:
--------------------------------
Description:
See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
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 entry?
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. But I have a cunning plan...
h4.Cunning Plan
We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take:
# Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it.
# Create a job in CI that runs just the recovery tests using your branch, containing the change above.
# Run regularly until it fails with this problem.
# Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build.
# Boot the AS and confirm that the issue is reproduced.
# You can now keep putting the tx-object-store back in place every time you need to reproduce the issue.
# Attach a debugger to find out what the problem is.
was:
See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
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 entry?
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.
> "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: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
> 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 entry?
> 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. But I have a cunning plan...
> h4.Cunning Plan
> We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take:
> # Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it.
> # Create a job in CI that runs just the recovery tests using your branch, containing the change above.
> # Run regularly until it fails with this problem.
> # Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build.
> # Boot the AS and confirm that the issue is reproduced.
> # You can now keep putting the tx-object-store back in place every time you need to reproduce the issue.
> # Attach a debugger to find out what the problem is.
--
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
11 years, 10 months