SOA JGroups Warning Messages on OC4J Default Group Logs Appear When TCP Option is Configured. (Doc ID 1251914.1)

Last updated on SEPTEMBER 25, 2013

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.3.1 to 10.1.3.5.0
Information in this document applies to any platform.

Symptoms

In SOA 10.1.3.3.1 (since MLR 11) to 10.1.3.5 clustered environment configured with the TCP option (in jgroups-protocol.xml) you get the following warning in the opmn log files:

Oct 11, 2010 6:33:33 PM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage
WARNING: discarded message from different group "GetXYZ-Adapter1.0"  ---> local group is DEV-GetABC-TW-Adapter1.0

The warning message (shown in code box above) has wrong Cluster Group Name, a name originating from another Cluster Group in cluster or Stand Alone SOA environments. Besides of the Warning message, in the oc4j default group files appears the following information:

Oct 12, 2010 12:08:09 AM org.collaxa.thirdparty.jgroups.protocols.UDP createSockets
INFO: socket information:
local_addr=10.1.16.66:55104, mcast_addr=224.0.0.35:45566, bind_addr=/10.1.16.66, ttl=32
sock: bound to 10.1.16.66:55104, receive buffer size=64000, send buffer size=32000
mcast_recv_sock: bound to 10.1.16.66:45566, send buffer size=150000, receive buffer size=80000
mcast_send_sock: bound to 10.1.16.66:55105, send buffer size=150000, receive buffer size=80000
Oct 12, 2010 12:08:09 AM org.collaxa.thirdparty.jgroups.protocols.TP handleIncomingMessage


And it the jgroups-protocol.xml was configured the TCP option:

<config>
<TCP start_port="7900" loopback="true" send_buf_size="32000" recv_buf_size="64000"/>
<TCPPING timeout="3000" initial_hosts="mynode1[7900],mynode2[7900]" port_range="3" num_initial_members="2"/>
<FD timeout="2000" max_tries="4"/>
<VERIFY_SUSPECT timeout="1500" down_thread="false" up_thread="false"/>
<pbcast.NAKACK gc_lag="100" retransmit_timeout="600,1200,2400,4800"/>
<pbcast.STABLE stability_delay="1000" desired_avg_gossip="20000" down_thread="false" max_bytes="0" up_thread="false"/>
<VIEW_SYNC avg_send_interval="60000" down_thread="false" up_thread="false" />
<pbcast.GMS print_local_addr="true" join_timeout="5000" join_retry_timeout="2000" shun="true"/>
</config>

 

Here the UDP with mcast_addr=224.0.0.35:45566 is used not matter if TCP option was configured in jgroups-protocol.xml file.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms