kie-drools-wb-6.5.0.Final on Wildfly 10 with 9990 connection failed error

[Ligong Xu]

Tried to setup multiple instances of kie-drools-wb  on the same linux box by changing the Wildfly port numbers through port-offset feature.  

In standalone-full.xml:

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

The wildfly seems started fine.  When I logged in workbench with the default uf-playground project, the server log showed the connection error. It was still referring to the default port 9990, not port 10190. I can verify that port 10190 is working fine for Wildfly console and management.  My question is where this port number can be configured  to the actual management port 10190.  I am also curious on what the application is trying to do with this management port using CLI commands.  

The stacktrace: 

2017-01-09 14:12:25,153 ERROR [org.uberfire.ext.security.management.wildfly10.cli.Wildfly10ModelUtil] (default task-61) Error reading realm using CLI commands.: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://127.0.0.1:9990. The connection failed

        at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)

        at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)

        at org.uberfire.ext.security.management.wildfly10.cli.Wildfly10ModelUtil.getPropertiesFilePath(Wildfly10ModelUtil.java:72)

...

Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://127.0.0.1:9990. The connection failed

        at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122)

        at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)

        at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)

        at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:218)

Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:

   JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Failed to read server challenge [Caused by java.io.FileNotFoundException: /home/alertdev/wildfly/standalone/tmp/auth/local894034627661319154.challenge (Permission denied)]

   DIGEST-MD5: java.lang.NullPointerException

        at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:114)

        at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:389)

        at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:241)

[Bernhard Benuli]

hi,

do you have a solution for this problem?

thanks

Bernhard

[Bernhard Benuli]

ok, solution is to set port at startup of server with vm parameter:

-Dorg.uberfire.ext.security.management.wildfly.cli.port=10190