domain.xml has the following excerpt:

<management-interfaces> <native-interface security-realm="ManagementRealm"> <socket interface="management" port="${jboss.management.native.port:9999}"/> </native-interface> The port should be changed to 9990 ?

Arun -- http://blog.arungupta.me http://twitter.com/arungupta _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On Tue, May 27, 2014 at 4:01 PM, Kabir Khan <kabir.khan(a)jboss.com&gt; wrote: > > On 27 May 2014, at 23:06, Arun Gupta <arun.gupta(a)gmail.com&gt; wrote: > >> domain.xml has the following excerpt: > host.xml? :-) >> Yes :-) >> <management-interfaces> >> <native-interface security-realm="ManagementRealm"> >> <socket interface="management" >> port="${jboss.management.native.port:9999}"/> >> </native-interface> >> >> The port should be changed to 9990 ? > > No, that is handled by the next interface > > <http-interface security-realm="ManagementRealm" http-upgrade-enabled="true"> > <socket interface="management" port="${jboss.management.http.port:9990}"/> > </http-interface> > > The native-interface one is there so that legacy HCs which don’t have the http-remoting protocol can connect back to the domain controller. host-slave.xml which is used on the slaves does not have the native interface enabled since it will only be connecting to a DC of the same version or newer. > https://docs.jboss.org/author/display/WFLY8/WildFly+8+Cluster+Howto still refer to JBoss AS 7. Where can I find the latest WildFly instructions that use host-slave.xml ?

Arun >> >> Arun >> >> >> -- >> http://blog.arungupta.me >> http://twitter.com/arungupta >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- http://blog.arungupta.me http://twitter.com/arungupta