Search code examples
serverjbosswildflysolaris

Error on starting the WildFly server (address already in use)

I have a problem starting a wildfly app-server (wildfly-21.0.1) on a Solaris server (computer). I have read a lot of similar posts, but my problem seems to be different. First, I make an SSH-tunnel in PuTTY: Session

Tunnels My home machine is Windows, I connect to a remote Solaris server. I write the address of the server in a "Host name" field. After this I create an SSH tunnel on a port of the server (I tried different and rare ones), so I put the port of the server I am connecting to in "Source port" field and the port of my personal machine (localhost:port_number) in the "Destination". I have configured standalone.xml by changing on

<interface name="public">
        <any-address/>
    </interface>

and

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

I have configured PATH and JAVA_HOME on the server. I start the server by

bash wildfly-21.0.1.Final/bin/standalone.sh

command. After this I get the following error:

 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: Address already in use /0.0.0.0:14384

It happens with any ports I tried, and I am sure that they aren't in use. How can I fix this? Are there any known bugs in Wildfly that can cause this? Is it somehow connected with tunneling?

Solution

  • The discussion with @AndrewHenle made me think of ports usage in a tunneling procedure so I changed "Remote" parameter in "Tunnels" section on "Local" (since the destination is localhost). All the other parameters and values were left the same. Now everything works correctly, and WildFly doesn't recognise 14384 as a taken port.