Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-4705

differences between registered and described operations for messaging resources in domain mode

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.2.Final (EAP)
    • None
    • Console, JMS
    • None

    Description

      The console does not give the same list of operation names for a messaging jms-topic resource when AS7 runs in standalone mode or domain mode.

      In standalone mode:

      [standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/jms-topic=testT/:read-operation-names
      {
          "outcome" => "success",
          "result" => [
              "add",
              "add-jndi",
              "count-messages-for-subscription",
              "drop-all-subscriptions",
              "drop-durable-subscription",
              "list-all-subscriptions",
              "list-all-subscriptions-as-json",
              "list-durable-subscriptions",
              "list-durable-subscriptions-as-json",
              "list-messages-for-subscription",
              "list-messages-for-subscription-as-json",
              "list-non-durable-subscriptions",
              "list-non-durable-subscriptions-as-json",
              "read-attribute",
              "read-children-names",
              "read-children-resources",
              "read-children-types",
              "read-operation-description",
              "read-operation-names",
              "read-resource",
              "read-resource-description",
              "remove",
              "remove-messages",
              "undefine-attribute",
              "whoami",
              "write-attribute"
          ]
      }
      

      In domain mode:

      [domain@localhost:9999 /]  /host=master/server=server-one/subsystem=messaging/hornetq-server=default/jms-topic=testT/:read-operation-names
      {
          "outcome" => "success",
          "result" => [
              "count-messages-for-subscription",
              "list-all-subscriptions",
              "list-all-subscriptions-as-json",
              "list-durable-subscriptions",
              "list-durable-subscriptions-as-json",
              "list-messages-for-subscription",
              "list-messages-for-subscription-as-json",
              "list-non-durable-subscriptions",
              "list-non-durable-subscriptions-as-json",
              "read-attribute",
              "read-children-names",
              "read-children-resources",
              "read-children-types",
              "read-operation-description",
              "read-operation-names",
              "read-resource",
              "read-resource-description"
          ]
      }
      

      I was expecting to have access to the same list of operations names using this address in domain mode than in standalone mode but some are missing (eg drop-all-subscriptions).

      However it is possible to perform the operation even when it is not displayed in the operation names:

      [domain@localhost:9999 /]  /host=master/server=server-one/subsystem=messaging/hornetq-server=default/jms-topic=testT/:read-operation-description(name="drop-all-subscriptions")
      {
          "outcome" => "failed",
          "result" => undefined,
          "failure-description" => "JBAS014753: There is no operation drop-all-subscriptions registered at address [
          (\"subsystem\" => \"messaging\"),
          (\"hornetq-server\" => \"default\"),
          (\"jms-topic\" => \"testT\")
      ]",
          "rolled-back" => true
      }
      [domain@localhost:9999 /]  /host=master/server=server-one/subsystem=messaging/hornetq-server=default/jms-topic=testT/:drop-all-subscriptions()
      {
          "outcome" => "success",
          "result" => undefined
      }
      

      Attachments

        Activity

          People

            jmesnil1@redhat.com Jeff Mesnil
            jmesnil1@redhat.com Jeff Mesnil
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: