[jboss-jira] [JBoss JIRA] (WFLY-7709) Native interface got left behind in standalone-minimalistic.xml config

Brian Stansberry (JIRA) issues at jboss.org
Mon Feb 20 21:54:00 EST 2017


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

Brian Stansberry updated WFLY-7709:
-----------------------------------
    Summary: Native interface got left behind in standalone-minimalistic.xml config  (was: Native interface got left behind standalone-minimalistic.xml config)


> Native interface got left behind in standalone-minimalistic.xml config
> ----------------------------------------------------------------------
>
>                 Key: WFLY-7709
>                 URL: https://issues.jboss.org/browse/WFLY-7709
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 10.1.0.Final
>            Reporter: Alexey Loubyansky
>            Assignee: Brian Stansberry
>
> Analyzing the lists of boot ops from the core and minimalistic configs, I've identified differences in the following operations.
> These operations are executed when the minimalistic config is loaded:
> {code}
>   /core-service=management/security-realm=ManagementRealm:add # map-groups-to-roles is true by default
>   /socket-binding-group=standard-sockets/socket-binding=management-http:add(interface="management",port="9990")
>   /socket-binding-group=standard-sockets/socket-binding=management-native:add(interface="management",port="\${jboss.management.native.port:9999}")
>   /core-service=management/management-interface=http-interface:add(console-enabled="false",security-realm="ManagementRealm",http-upgrade={"enabled" => true},socket-binding="management-http")
>   /core-service=management/management-interface=native-interface:add(security-realm="ManagementRealm",socket-binding="management-native") # UNIQUE
>   /socket-binding-group=standard-sockets:add(default-interface="public")
> {code}
> These operations are executed as part of the default core config:
> {code}
>   /core-service=management/security-realm=ManagementRealm:add(map-groups-to-roles="false")
>   /socket-binding-group=standard-sockets/socket-binding=management-http:add(interface="management",port="\${jboss.management.http.port:9990}") # accepts system prop
>   /socket-binding-group=standard-sockets/socket-binding=management-https:add(interface="management",port="\${jboss.management.https.port:9993}") # https instead of native
>   /core-service=management/management-interface=http-interface:add(security-realm="ManagementRealm",http-upgrade={"enabled" => true},socket-binding="management-http") # console-enabled is true by default
>   /socket-binding-group=standard-sockets:add(default-interface="public",port-offset="\${jboss.socket.binding.port-offset:0}") # accepts system prop
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list