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

Adding JGroups stack hangs the server

    XMLWordPrintable

Details

    • Hide
      1. Run Wildfly in domain mode
      2. Navigate to JGroups stack table in web console: Configuration -> Profiles -> full-ha -> JGroups and click on View
      3. Click on Add button
      4. Fill form in wizard
        1. Fill random name
        2. Choose UDP transport
        3. Fill random socket binding (e.g. asdfasdf)
      5. Click on Next button
      6. Fill form in wizard
        1. Select UNICAST2 name
        2. Fill random socket binding (e.g. gfsdfgsg)
        3. Click on Append button
      7. Click on Done button
      8. Web Console is now frozen (try for example click on back arrow and then selecting any subsystem)
      Show
      Run Wildfly in domain mode Navigate to JGroups stack table in web console: Configuration -> Profiles -> full-ha -> JGroups and click on View Click on Add button Fill form in wizard Fill random name Choose UDP transport Fill random socket binding (e.g. asdfasdf) Click on Next button Fill form in wizard Select UNICAST2 name Fill random socket binding (e.g. gfsdfgsg) Click on Append button Click on Done button Web Console is now frozen (try for example click on back arrow and then selecting any subsystem)
    • Hide

      The address of the transport changed in WF9. The workaround is to use the new address of the transport, not the legacy address, e.g. /subsystem=jgroups/stack=foo/transport=UDP

      Show
      The address of the transport changed in WF9. The workaround is to use the new address of the transport, not the legacy address, e.g. /subsystem=jgroups/stack=foo/transport=UDP

    Description

      Adding new JGroups stack with randomly chosen (non existing) socket binding name results in web console freeze.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-871 Adding JGroups stack results in freeze

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users WFCORE-1022 AliasEntry needs more information than just the PathAddress

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1034 2 step domain operations do not resolve aliases properly

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              jkasik@redhat.com Jan Kašík
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: