[jboss-jira] [JBoss JIRA] (AS7-5011) Unable to save network interface configuration

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated AS7-5011:
----------------------------------

    Component/s: Domain Management


What happens if you skip the 

{"operation":"write-attribute","address":[{"interface":"management"}],"name":"any-address","value":false},{"operation":"write-attribute","address":[{"interface":"public"}],"name":"any-ipv4-address","value":false}

bits?  (Skip them for the "public" interface as well.

Also, what it the Affects Version?
                
> Unable to save network interface configuration
> ----------------------------------------------
>
>                 Key: AS7-5011
>                 URL: https://issues.jboss.org/browse/AS7-5011
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Stefan Negrea
>
> A standalone server is successfully started with the following entry for the network interfaces (management interface picked as an example):
>  <interfaces>
>         <interface name="management">
>             <loopback-address value="${jboss.bind.address.management:127.0.0.1}"/>
>         </interface>
>   ......
> JSON read for the management network interface:
> {"outcome" : "success", "result" : {"any" : null, "any-address" : null, "any-ipv4-address" : null, "any-ipv6-address" : null, "inet-address" : null, "link-local-address" : null, "loopback" : null, "loopback-address" : { "EXPRESSION_VALUE" : "${jboss.bind.address.management:127.0.0.1}" }, "multicast" : null, "name" : "management", "nic" : null, "nic-match" : null, "not" : null, "point-to-point" : null, "public-address" : null, "site-local-address" : null, "subnet-match" : null, "up" : null, "virtual" : null}, "response-headers" : {"process-state" : "reload-required"}}
> JSON to update the management network interface:
> {"operation":"composite","steps":[{"operation":"write-attribute","address":[{"interface":"management"}],"name":"any-address","value":false},{"operation":"write-attribute","address":[{"interface":"public"}],"name":"any-ipv4-address","value":false},{"operation":"write-attribute","address":[{"interface":"public"}],"name":"any-ipv6-address","value":false},{"operation":"write-attribute","address":[{"interface":"public"}],"name":"loopback-address","value":"${jboss.bind.address.management:127.0.0.1}"}],"address":[]}
> Received the following error during update:
> {JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-4=JBAS014677: Failed to persist configuration change: JBAS014675: Failed to marshal configuration}}, rolled-back=true
> The purpose of this attempt is to read the configuration of a resource and write it back as it. This obviously fails but the problem is that the server is correctly started with the configuration. So the configuration is invalid for updates but is valid for start-up?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira