9 Replies Latest reply on Apr 29, 2016 1:20 AM by Guru Prashanth Thanakodi

    Could not connect to remote port

    Guru Prashanth Thanakodi Newbie




      I am trying to change the log level from info to debug in the standalone.xml configuration file during run time using the ModelControllerClient. But I am unable to connect to the native interface. It fails with the error Could not connect to remote port. I am using WildFly 9.0.0.Final . If I use the configuration mentioned in this page, WildFly fails to start saying invalid attribute interface. Can someone tell me what's wrong in the confugration?





      Here is the configuration in the standalone.xml file


      <native-interface  security-realm="ManagementRealm">

        <socket-binding native="management-native"/>




      Section referring to management-native:


      <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

              <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>

              <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>

            <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>







      Here is the code to do that.


      client = ModelControllerClient.Factory.create(

               InetAddress.getByName(""), 9999);  // NOSONAR