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

Failing RemoteFailoverTestCase#testStatefulFailover when transaction run under JTS

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.0.0.ER6
    • 7.0.0.ER3
    • Clustering, Test Suite
    • None
    • 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.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-6160 Failing RemoteFailoverTestCase#testStatefulFailover when transaction run under JTS

          • 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.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1954 InfinispanBatchContext trying to resume committed tx

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1634 Failing tests of AS testsuite StatefulFailoverTestCase and CdiFailoverTestCase when JTS transactions are used

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Ondrej Chaloupka Ondrej Chaloupka (Inactive)
              Ondrej Chaloupka Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: