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

[GSS] HAL-1584 - WFLYCTL0030 when getting queue detail in HAL in domain mode

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • 7.2.0.GA
    • Web Console
    • Workaround Exists
    • Hide

      using CLI, or ignoring the error

      Show
      using CLI, or ignoring the error
    • Hide
      • Start domain controller:
        bin/domain.sh --domain-config=domain.xml --host-config=host-master.xml
      • Start host controller:
        bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1
      • Browse to Runtime->hosts->"host name" >server one>messaging-activemq->default, then click on DLQ: the error will show on the screen. you can get the detail by hitting "details"
      Show
      Start domain controller: bin/domain.sh --domain-config=domain.xml --host-config=host-master.xml Start host controller: bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 Browse to Runtime->hosts->"host name" >server one >messaging-activemq->default, then click on DLQ: the error will show on the screen. you can get the detail by hitting "details"

      Using HAL in domain mode to get jms queue detail, the error
      "WFLYCTL0030: NO resource definition is registered for address"

      1- When trying to obtain all reqiurces of a queue through CLI, it works fine:

      /host=mohameds-mbp.t-mobile.com/server=server-one/subsystem=messaging-activemq/server=default/jms-queue=DLQ:read-resource(include-runtime=true, recursive=true)
      {
      "outcome" => "success",
      "result" =>

      { "consumer-count" => 0, "dead-letter-address" => "jms.queue.DLQ", "delivering-count" => 0, "durable" => true, "entries" => ["java:/jms/queue/DLQ"], "expiry-address" => "jms.queue.ExpiryQueue", "legacy-entries" => undefined, "message-count" => 0L, "messages-added" => 0L, "paused" => false, "queue-address" => "jms.queue.DLQ", "scheduled-count" => 0L, "selector" => undefined, "temporary" => false }

      }

      2- When doing the same in standalone mode, no error is shown in HAL

        1. snap1.jpg
          snap1.jpg
          111 kB
        2. snap2.png
          snap2.png
          38 kB

            thofman Tomas Hofman
            rhn-support-abelkour Mohamed Amine Belkoura
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: