Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-7765

failing test InboundCrashRecoveryTests

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.4.CR2, 7.0.4.GA
    • 7.0.4.CR1
    • Transactions
    • None
    • Regression
    • Hide

      git clone git@github.com:jbosstm/narayana.git

      git checkout 5.2.20.Final

      export JBOSS_HOME=...

      cp $JBOSS_HOME/docs/examples/configs/standalone-xts.xml $JBOSS_HOME/standalone/configuration/

      sed -i 's/(<recovery-environment )/\1 recovery-listener="true" /' $JBOSS_HOME/standalone/configuration/standalone-xts.xml

      cd txbridge

      mvn clean install -Parq -Dtest=InboundCrashRecoveryTests

      Show
      git clone git@github.com:jbosstm/narayana.git git checkout 5.2.20.Final export JBOSS_HOME=... cp $JBOSS_HOME/docs/examples/configs/standalone-xts.xml $JBOSS_HOME/standalone/configuration/ sed -i 's/(<recovery-environment )/\1 recovery-listener="true" /' $JBOSS_HOME/standalone/configuration/standalone-xts.xml cd txbridge mvn clean install -Parq -Dtest=InboundCrashRecoveryTests
    • EAP 7.0.4

    Description

      failing test InboundCrashRecoveryTests:

      Error Message

      • required minimum call count 1 but was 0

      Stacktrace

      java.lang.AssertionError: - required minimum call count 1 but was 0
      at org.junit.Assert.fail(Assert.java:88)
      at org.junit.Assert.assertTrue(Assert.java:41)
      at org.jboss.byteman.contrib.dtest.InstrumentedInstance.assertMethodCallCount(InstrumentedInstance.java:92)
      at org.jboss.byteman.contrib.dtest.InstrumentedClass.assertMethodCallCount(InstrumentedClass.java:112)
      at org.jboss.byteman.contrib.dtest.InstrumentedClass.assertMethodCalled(InstrumentedClass.java:124)
      at org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests.testCrashThreeLogs(InboundCrashRecoveryTests.java:212)

      Attachments

        Issue Links

          incorporates

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBTM-2701 Allow in-flowed XAR to be scanned for Xid more than once between scans of the recovery system

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is caused by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-6395 [GSS](7.0.z) Upgrade JBoss Transaction Manager from 5.2.17 to 5.2.20

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-7819 (7.0.z) Upgrade JBoss Transaction Manager from 5.2.20 to 5.2.21

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              thjenkin@redhat.com Tom Jenkinson
              jbilek@redhat.com Jiří Bílek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: