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#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...