Bug 1467848

Summary: [GSS](6.4.z) CLI to add a socket-binding fails first time
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Girish Andavarapu <gandavar>
Component: CLIAssignee: Jiri Ondrusek <jondruse>
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.16CC: bbaranow, bmaxwell, brian.stansberry, dcihak, dconsoli, gandavar, jboss-set, jondruse, rstancel, shsingh
Target Milestone: CR1   
Target Release: EAP 6.4.21   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:42:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1567790    

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 /]