Agent will not start - failed tojoin the existing coherence cluster node
book
Article ID: KB0093881
calendar_today
Updated On:
Products
Versions
TIBCO BusinessEvents Enterprise Edition
-
Not Applicable
-
Description
Resolution: Description: =========== Agent will not start - failed to join the existing coherence cluster node
Environment: =========== BusinessEvents 4.0.1 All Operating Systems
Symptoms: ========= BusinessEvents log reports error: java.lang.RuntimeException: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINED)
Coherence log includes warning: Oracle Coherence EE 3.6.0.0 <Warning> (thread=main, member=n/a): PreferredUnicastUdpSocket failed to set receive buffer size to 1428 packets (22.3MB); actual size is 0%, 7 packets (127KB). Consult your OS documentation regarding increasing the maximum socket buffer size. Proceeding with the actual value may cause sub-optimal performance. Oracle Coherence EE 3.6.0.0 <Warning> (thread=main, member=n/a): MulticastUdpSocket failed to set send buffer size to 357 packets (511KB); actual size is 25%, 89 packets (127KB). Consult your OS documentation regarding increasing the maximum socket buffer size. Proceeding with the actual value may cause sub-optimal performance.
Oracle Coherence EE 3.6.0.0 <Warning> (thread=main, member=n/a): IPMonitor has been explicitly disabled, this is not a recommended practice and will result in a minimum death detection time of 300 seconds for failed machines or networks.
Cause: ====== Operating System packet-size is too small.
NOTE: To test if large packets are working use the command:
"ping -s <size> <host>"
example:
ping -s 123474 testserver
Resolution: ======== There are 2 options to solve the issue.
1.) Limit the packet-size used by Coherence (which may impact on performance) by adding the max packet-size to tangosol-coherence.xml (in <BE-HOME>/lib/ext/coherence.jar) in <packet-publisher>.