[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-2394 - multicast addr not working
by dimitris@jboss.org
Related to http://jira.jboss.com/jira/browse/JBAS-2398
I tried running latest jboss 4.x in all 3 configurations, on a WinXP box, using ./run and ./run -b <local-nic>, checking the listening ports with TCPView.
In the minimal & default config, run -b binds all listening ports to the specified address.
In the all config, run -b shows the folowing addresses bound to 0.0.0.0
cluster-service.xml
---------------------------
UDP 0.0.0.0:1102 (${jboss.partition.udpGroup:230.0.0.4}, 1102) - ha-jndi
UDP 0.0.0.0:45566 (${jboss.partition.udpGroup:228.1.2.3}, 45566)
TCP 0.0.0.0:49153 (fixed tcp port)
UDP 0.0.0.0:2807 (random udp port)
tc5-cluster.sar
--------------------------
UDP 0.0.0.0:45577 (${jboss.partition.udpGroup:230.1.2.3}, 45577)
TCP 0.0.0.0:49152 (fixed tcp port)
UDP 0.0.0.0:2804 (random udp port)
1) It seems to me that although the bound multicast UDP sockets are reported to be bound to 0.0.0.0, they are clearly configured with 230.0.0.4, 228.1.2.3, 230.1.2.3, so this seems like a winxp thing we could ignore ?
2) Both jgroup stacks, listen also to 1 fixed tcp port, and 1 random udp port each. What are exactly those and shouldn't (at least the TCP port) be bound to the ${jboss.bind.address} ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962801#3962801
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962801
17 years, 9 months
[Design of JBoss/Tomcat Integration] - Forwarding from apache -> jboss -> jboss
by pmm258
In the screnaio where there is an apache in a DMZ forwarding to a known JBoss AJP13 port using mod-jk. This is works fine as per doco.
We have scenario where we deploy an application to another 'offline' jboss instance with different ports and when testing is complete and ready for deployment switch we have to change the worker.properties settings on DMZ apache server.
The DMZ apache server is under the control of another section, making changes more difficult.
Is it possible to have an intermediate JBoss instance always listening on a known AJP port (say 9002) for the DMZ apache server, to forward to the real JBoss instance on a port specified in the intermediate JBoss instance.
Changing the intermediate JBoss to forward to the different port would be more under our control.
Are there any other options in doing this 2 step forwarding ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962665#3962665
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962665
17 years, 9 months