Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6160

Failing RemoteFailoverTestCase#testStatefulFailover when transaction run under JTS

    XMLWordPrintable

    Details

    • Steps to Reproduce:
      Hide
      1. download JBoss EAP7 ER5
      2. unzip and set JBOSS_HOME to that directory
      3. change standalone/configuration/standalone-full-ha.xml to enable jts transactions
        1. change attribute transactions iiop-openjdk subsystem to value full
        2. add element <jts/> under transactions subsystem
      4. take EAP sources and run integration test
        1. ./integration-tests.sh clean install -Dts.noSmoke -Dts.clustering -Djboss.dist=$JBOSS_HOME -Dtest=RemoteFailoverTestCase#testStatefulFailover
      Show
      download JBoss EAP7 ER5 unzip and set JBOSS_HOME to that directory change standalone/configuration/standalone-full-ha.xml to enable jts transactions change attribute transactions iiop-openjdk subsystem to value full add element <jts/> under transactions subsystem take EAP sources and run integration test ./integration-tests.sh clean install -Dts.noSmoke -Dts.clustering -Djboss.dist=$JBOSS_HOME -Dtest=RemoteFailoverTestCase#testStatefulFailover

      Description

      I can see failing test RemoteFailoverTestCase#testStatefulFailover when transactions are set to run under JTS. I'm not sure if this is a trouble of clustering component or only a testsuite issue.

      This could be connected with JBEAP-1954.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  ochaloup Ondrej Chaloupka
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: