-
1. Re: wildfly standalone-ha cluster with mod_cluster port-offset not working
rhusar Aug 21, 2013 4:14 AM (in response to shadogray)For some reason the port offset didnt seem to kick in, I ll take a look why.
But you can just start the second node with
-Djboss.ajp.port=8109
and it will do the job.
-
2. Re: wildfly standalone-ha cluster with mod_cluster port-offset not working
rhusar Aug 21, 2013 4:16 AM (in response to rhusar)Tried port offset on Beta1-SNAPSHOT and it works fine:
10:14:50,979 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017519: Undertow AJP listener ajp listening on /127.0.0.1:8109
Make sure you are setting right property:
-Djboss.socket.binding.port-offset=100
or XML:
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:100}">
-
3. Re: wildfly standalone-ha cluster with mod_cluster port-offset not working
shadogray Aug 21, 2013 4:35 PM (in response to rhusar)Thanks Radoslav, that did it.
Regards,
Thomas
-
4. Re: wildfly standalone-ha cluster with mod_cluster port-offset not working
shadogray Aug 23, 2013 6:13 PM (in response to rhusar)Sorry Radoslav, it looked as if it worked first. Unfortunately it doesnt really.
I use Wildfly Beta1 Snapshot.
Second command line:
bin/standalone.sh -c standalone-ha.xml -b localhost -Djboss.socket.binding.port-offset=100 -Djboss.node.name=NodeB -Djboss.mod_cluster.jvmRoute=NodeB -Djboss.ajp.port=8109
After starting 2 Servers (standalone-ha) both are shown in the mod_cluster-manager, but after shutdown of NodeA the service is totally unavailable:
[Sat Aug 24 00:09:45 2013] [error] (111)Connection refused: proxy: ajp: attempt to connect to 127.0.0.1:8109 (localhost) failed
[Sat Aug 24 00:09:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Sat Aug 24 00:09:45 2013] [error] proxy: ajp: disabled connection for (localhost)and netstat shows:
# netstat -an |grep 09
tcp 0 0 127.0.0.1:8209 0.0.0.0:* LISTENAs it seems, internally the port is not correctly managed, adding jboss.ajp.port helps mod_cluster, but port-offset ruins the effect.
-
5. Re: Re: wildfly standalone-ha cluster with mod_cluster port-offset not working
rhusar Aug 26, 2013 4:43 AM (in response to shadogray)Oh well, AJP is completely broken in the SNAPSHOT, see:
Sorry about that.
Specifying both ajp.port and port-offset together will work in a way, that first the ajp port will be overriden and then the offset will be added. So that's not really what you want. But it indicates that just using port-offset should do the job for you.