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

Can not create messaging clustering connection

    XMLWordPrintable

Details

    • Hide

      1.Run EAP 7.0.0 DR9 in standalone mode with standalone-full-ha profile
      2.Go to configuration, subsystems, messaging , default ,clustering, connections a try to add connection
      3.It is not possible because of error with connection name

      Show
      1.Run EAP 7.0.0 DR9 in standalone mode with standalone-full-ha profile 2.Go to configuration, subsystems, messaging , default ,clustering, connections a try to add connection 3.It is not possible because of error with connection name

    Description

      Can not create cluster connection in subsystem, messaging, defulat, clustering, connecitons. Connection-ref in creation window is form EAP 6 and now it is connection-name.

      Unexpected HTTP response: 500
      
      Request
      {
          "cluster-connection-address" => "jms",
          "connector-ref" => "http-connector",
          "discovery-group-name" => "dg-group1",
          "forward-when-no-consumers" => false,
          "use-duplicate-detection" => false,
          "address" => [
              ("subsystem" => "messaging-activemq"),
              ("server" => "default"),
              ("cluster-connection" => "test")
          ],
          "operation" => "add"
      }
      
      Response
      
      Internal Server Error
      {
          "outcome" => "failed",
          "failure-description" => "WFLYCTL0155: connector-name may not be null",
          "rolled-back" => true,
          "response-headers" => {"process-state" => "reload-required"}
      }
      

      Attachments

        Issue Links

          Activity

            People

              thofman Tomas Hofman
              pcyprian_jira Patrik Cyprian (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: