Bug 1467848 - CLI to add a socket-binding fails first time
CLI to add a socket-binding fails first time
Status: POST
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI (Show other bugs)
6.4.16
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jiri Ondrusek
Peter Mackay
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-05 06:30 EDT by Girish Andavarapu
Modified: 2017-07-13 08:49 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Girish Andavarapu 2017-07-05 06:30:10 EDT
Description of problem:

EAP 6.4 : (BUG) first command fails, but the same syntax works for second command, the result is the same if the order of the commands is switched.

[standalone@localhost:9999 /] command add --node-type=/socket-binding-group=standard-sockets/socket-binding --command-name=socketbinding
[standalone@localhost:9999 /]  socketbinding add --name=messaging-throughput --port=5455
Failed to handle 'socketbinding add --name=messaging-throughput --port=5455': java.lang.IllegalArgumentException
[standalone@localhost:9999 /] socketbinding add --name=messaging --port=5445
[standalone@localhost:9999 /]



EAP 7 : (Works fine in EAP 7)

[standalone@localhost:9990 /] command add --node-type=/socket-binding-group=standard-sockets/socket-binding --command-name=socketbinding
[standalone@localhost:9990 /] socketbinding add --name=messaging-throughput --port=5455
[standalone@localhost:9990 /] socketbinding add --name=messaging --port=5445
[standalone@localhost:9990 /]

Note You need to log in before you can comment on or make changes to this bug.