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

(7.4.z) Fix testsuite/integration/multinode failures on SE 17

    XMLWordPrintable

Details

    Description

      Running the testsuite on SE 17 against the branches being used for JBEAP-22556 / EAP7-1624 results in the multinode testsuite failing.

      It's odd because if I run the testsuite module with SE 8 and then run with SE 17 it passes, except for 3 failures in DynamicJNDIContextEJBInvocationTestCase. The RTS testsuite shows the same pattern; see JBEAP-22870.

      Anyone looking into this should contact bstansbe@redhat.com before starting for more context; otherwise you'll likely waste time.

      Attachments

        Issue Links

          clones

          Task - Represents a small unit of work that is not end-user facing. JBEAP-22870 (7.4.z) Fix testsuite/integration/rts failures on SE 17

          • 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 blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-23097 (7.4.z) Elytron local authentication doesn't work if no standalone/tmp/auth dir exists and no legacy security-realm is configured

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. JBEAP-22873 (7.4.z) Fix testsuite/integration/domain failures on SE 17

          • 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

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: