Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-1970

Exception when viewing datasources in Management Console

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • Flow Control, ux
    • None
    • Hide
      1. Start WildFly server in domain mode
      2. Two servers, each using its own profile
      3. A non-xa datasource in one profile, an XA datasource in the other
      4. Navigate to management console and view one of the datasources
      5. Switch to view the other datasource

      Direct:

      1. drop provided conf into WFLY 32B+ build
      2. enable network
      3. add mgmt user if needs be
      4. ./bin/domain.sh
      5. http://localhost:9090
      6. Navigate "top" -> runtime
      7. Navigate Hosts->primary->server-one->datasources->oracle + "View"
      8. Navigate like above but into DS on server-two - this should KABOOM
      9. Above are interchangeable
      Show
      Start WildFly server in domain mode Two servers, each using its own profile A non-xa datasource in one profile, an XA datasource in the other Navigate to management console and view one of the datasources Switch to view the other datasource Direct: drop provided conf into WFLY 32B+ build enable network add mgmt user if needs be ./bin/domain.sh http://localhost:9090 Navigate "top" -> runtime Navigate Hosts->primary->server-one->datasources->oracle + "View" Navigate like above but into DS on server-two - this should KABOOM Above are interchangeable

    Description

      This is essentially either design flaw or setup. What happens is ModelNodeForm is created and shared between views. Name template is being reused between views, which is bad. Check comments in WFLY for detialed description.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26714 [GSS](8.0.z) HAL-1970 - Exception when viewing datasources in Management Console

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFLY-18953 Exception when viewing datasources in Management Console

          • 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.
          • Resolved
          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26463 [GSS](7.4.z) HAL-1970 - Exception when viewing datasources in Management Console

          • 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.
          • Ready for QA

          Activity

            People

              hpehl@redhat.com Harald Pehl
              rhn-cservice-bbaranow Bartosz Baranowski
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: