Bug 1467848 - [GSS](6.4.z) CLI to add a socket-binding fails first time
Summary: [GSS](6.4.z) CLI to add a socket-binding fails first time
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.4.16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.21
Assignee: Jiri Ondrusek
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: eap6421-payload
TreeView+ depends on / blocked
 
Reported: 2017-07-05 10:30 UTC by Girish Andavarapu
Modified: 2021-12-10 15:08 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:42:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Girish Andavarapu 2017-07-05 10:30:10 UTC
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.