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

Some uids left in ts-log during LRCO transaction scenario

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • Transactions
    • None
    • False
    • None
    • False

      Some uids left in ts-log during the "Halts server at commit phase on TestXAResource after commit was invoked on JPA/JMS XA resource." scenario involving a standard JMS resource and expecting LRCO will be used:

      1. enlist XA resource
      2. enlist TestXA resource
      3. prepare XA resource
      4. prepare TestXA resource
      5. commit XA resource
      6. JVM crash
      7. recovery started
      8. commit TestXA resource
      java.lang.AssertionError: Recovery failed, some Uids still left in the tx log - number of pending uids before test: 0, pending uids after test: 1. Pending Uids are: [0:ffff7f000001:-2dd2fce6:676202c6:53]
	at org.junit.Assert.fail(Assert.java:89)
	at org.jboss.as.test.jbossts.base.TestBaseOneServer.checkIfTransactionManagerLogStoreIsEmpy(TestBaseOneServer.java:644)
	at org.jboss.as.test.jbossts.base.TestBaseOneServer.checkIfTxLogsAreEmpty(TestBaseOneServer.java:589)
	at org.jboss.as.test.jbossts.crashrec.test.TestBaseCrashRecovery.commitHaltTest(TestBaseCrashRecovery.java:487)
	at org.jboss.as.test.jbossts.crashrec.test.TestBaseCrashRecovery.commitHaltFirst(TestBaseCrashRecovery.java:391)

      The issue has been caused by (cc rhn-engineering-mmusgrov)

      This issue is a blocker, because it's a regression against EAP 8.0.

              rhn-engineering-mmusgrov Michael Musgrove
              mkopecky@redhat.com Marek Kopecky
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: