[jboss-jira] [JBoss JIRA] (AS7-2599) The socket-binding-port-offset can be set in CLI without defining socket-binding-group

[Brian Stansberry (Resolved) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved AS7-2599.
-----------------------------------

    Resolution: Done


The socket binding config in the host.xml <server> element is now:

<socket-bindings socket-binding-group="thegroup" port-offset="100"/>

Neither attribute is required; if socket-binding-group is not set, the value from the server-group is used. No port-offset is the same as 0.

This has no impact on the management API; it just brings the xml in line with how the management API behaves.
                
> The socket-binding-port-offset can be set in CLI without defining socket-binding-group
> --------------------------------------------------------------------------------------
>
>                 Key: AS7-2599
>                 URL: https://issues.jboss.org/browse/AS7-2599
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Rich Raposa
>            Assignee: Brian Stansberry
>            Priority: Blocker
>             Fix For: 7.1.0.CR1
>
>
> The following CLI command works:
> /host=myhost/server-config=myserver:add(group=group-name,socket-binding-port-offset=2000)
> but the offset of 2000 is ignored (does not appear in host.xml). I realize it doesn't make sense to define an offset without a socket-binding-group defined as well. I think the CLI command should have failed and displayed a message like "socket-bind-port-offset requires a socket-binding-group to be defined" or something like that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira