-
1. Re: Wildfly 9.0.2 socket-binding problem with port in use for remote
mdelson Nov 30, 2015 5:24 AM (in response to marlowa42)attaching your standalone.xml should help.
below is what I have in the socket-binding section
================
<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="ajp" port="${jboss.ajp.port:8009}"/>
<socket-binding name="http" port="${jboss.http.port:8180}"/>
<socket-binding name="https" port="${jboss.https.port:8443}"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
</socket-binding-group>
================
-
2. Re: Wildfly 9.0.2 socket-binding problem with port in use for remote
ctomc Nov 30, 2015 8:26 AM (in response to mdelson)Well given that original question doesn't provide the context (log) of "port already in use" it is impossible to tell what port is already in use.
so changing just http listner port wouldn't help if port in question is different to start with.
so in short, best way to run multiple wildfly instances on same machine is using port-offset instead of manually updating few socket bindings.
see good blog post on this topic http://blog.arungupta.me/multiple-instances-wildfly-different-ports-same-machine-tech-tip-8/
in short all you need to do is to add
-Djboss.socket.binding.port-offset=10
with port offset of 10, http server will be available on 8090 for example.