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

In Managed domain , accessing the ActiveMQ subsystem via the server group on managemnet console gives an HTTP 500

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.1.0.DR14
    • 7.0.4.GA
    • Web Console
    • None
    • Workaround Exists
    • Hide

      Browse Domain By Hosts instead of Server Groups.

      Show
      Browse Domain By Hosts instead of Server Groups.
    • Hide

      Check Description and I have attached a screen-shot.

      Show
      Check Description and I have attached a screen-shot.

      In a managed domain , accessing the ActiveMQ subsystem via the server group (Server Groups > Server Group: main-server-group > Server: Host1 > Monitor: Subsystems > Subsystem: Messaging - ActiveMQ) gives an HTTP 500 error with the following contents

      Unexpected HTTP response: 500
      
      Request
      {
          "operation" => "read-children-resources",
          "address" => [
              ("host" => "host"),
              ("server" => "Master1"),
              ("subsystem" => "messaging-activemq")
          ],
          "child-type" => "server"
      }
      
      Response
      
      Internal Server Error
      {
          "outcome" => "failed",
          "result" => undefined,
          "failure-description" => "WFLYCTL0030: No resource definition is registered for address [
          (\"host\" => \"host\"),
          (\"server\" => \"Master1\"),
          (\"subsystem\" => \"messaging-activemq\")
      ]",
          "rolled-back" => true
      }
      

      The server Master1 is on host master, DMR generated use the last host name.

        1. Bug1.png
          Bug1.png
          169 kB
        2. host-master.xml
          8 kB

            thofman Tomas Hofman
            rhn-support-shsingh Shailendra Singh
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: