[jboss-jira] [JBoss JIRA] (AS7-4705) differences between registered and described operations for messaging resources in domain mode
RH Bugzilla Integration (JIRA)
issues at jboss.org
Wed Aug 6 10:40:35 EDT 2014
[ https://issues.jboss.org/browse/AS7-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990806#comment-12990806 ]
RH Bugzilla Integration commented on AS7-4705:
----------------------------------------------
Pavel Slavicek <pslavice at redhat.com> changed the Status of [bug 1097770|https://bugzilla.redhat.com/show_bug.cgi?id=1097770] from VERIFIED to CLOSED
> differences between registered and described operations for messaging resources in domain mode
> ----------------------------------------------------------------------------------------------
>
> Key: AS7-4705
> URL: https://issues.jboss.org/browse/AS7-4705
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 7.1.2.Final (EAP)
>
>
> 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:
> {noformat}
> [standalone at 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"
> ]
> }
> {noformat}
> In domain mode:
> {noformat}
> [domain at 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"
> ]
> }
> {noformat}
> 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:
> {noformat}
> [domain at 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 at localhost:9999 /] /host=master/server=server-one/subsystem=messaging/hornetq-server=default/jms-topic=testT/:drop-all-subscriptions()
> {
> "outcome" => "success",
> "result" => undefined
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the jboss-jira
mailing list