Error message in opmn OC4J log for my BPEL cluster setup

Question

I am settings up my 2 nodes BPEL cluster in the same subnet, i prepared my jgroups-protocols.xml as:
<config>
<UDP mcast_send_buf_size="32000"
mcast_port="45788"
ucast_recv_buf_size="64000"
mcast_addr="228.8.15.24"
receive_on_all_interfaces="true"
loopback="true"
mcast_recv_buf_size="64000"
max_bundle_size="48000"
max_bundle_timeout="30"
use_incoming_packet_handler="false"
use_outgoing_packet_handler="false"
ucast_send_buf_size="32000"
ip_ttl="32"
enable_bundling="false"/>
<PING timeout="2000"
num_initial_members="3"/>
<MERGE2 max_interval="10000"
min_interval="5000"/>
<FD timeout="2000"
max_tries="3"
shun="true"/>
<VERIFY_SUSPECT timeout="1500"/>
<pbcast.NAKACK max_xmit_size="8192"
use_mcast_xmit="false"
gc_lag="50"
retransmit_timeout="600,1200,2400,4800"/>
<UNICAST timeout="1200,2400,3600"/>
it is same as the default file, the configuration is same in both nodes, however, in OC4J log, i found it return the address is already in use:
zed adaptors for platform 'ias_10g'
Feb 22, 2008 2:58:17 PM org.collaxa.thirdparty.jgroups.protocols.UDP createSockets
INFO: sockets will use interface 0.0.0.0
08/02/22 14:58:17 java.lang.Exception: exception caused by UDP.start(): java.net.SocketException: Address already in use
08/02/22 14:58:17 at org.collaxa.thirdparty.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:600)
08/02/22 14:58:17 at org.collaxa.thirdparty.jgroups.stack.DownHandler.run(Protocol.java:117)
<2008-02-22 14:58:18,453> <INFO> <collaxa> <ServerManager::uninit> Shutting down all domains
<2008-02-22 14:58:18,453> <INFO> <collaxa> <ServerManager::uninit> Done shutting down all domains
<QuartzPublisherInit::init> Notification Retry publisher scheduled at every 15 minute(s)
08/02/22 14:59:18 Oracle Containers for J2EE 10g (10.1.3.3.0) initialized
what is the problem ? how to fix it ?
thanks.

Answer 1

Hi,
Remove "receive_on_all_interfaces" and set bind_to_all_interfaces=false i think.
It might not be exactly what you want to do, but read up on those parameters on the internet on Jgroups.