Details
-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.Final, 7.0.1.Final
Description
Looks to me that the CLI is behaving differently if you are running in a domain mode or in a stadnalone mode managing just a host. However it is not really clear from the CLI help messages.
In the following log
- the console does not say its running in the domain mode
- claims that the --profile argument is optional even though its indeed required
- does not say that it is not the master domain controller and refuses all changes anyway
[domain@rhusar:9999 /] add-jms-queue --help Synopsis: add-jms-queue [--profile=profile_name] --name=queue_name [--entries=entry(,entry)*] [--selector=selector_name] [--durable=(true|false)] Description: creates a JMS queue Arguments: profile - is allowed and required only in the domain mode, specifies the profile in which the JMS resource should be created. name - the name of the queue. entries - an optional comma-separated list of JNDI names the queue should be bound under. If not present, the name will be used as the JNDI name. selector - optional selector. durable - optional, specifies whether the queue should be durable or not (the default is true). [domain@rhusar:9999 /] add-jms-queue --profile=ha --name=rQ Operation add for address [ ("profile" => "ha"), ("subsystem" => "messaging"), ("jms-queue" => "rQ") ] can only handled by the master Domain Controller; this host is not the master Domain Controller [domain@rhusar:9999 /] add-jms-queue --name=rQ --profile argument value is missing. [domain@rhusar:9999 /] quit Closed connection to rhusar:9999
