Highlighted
Community Manager changl Community Manager
Community Manager
263 views

(PPM) Support Tip: Criteria to switch JGroups channels to TCP mode

Out of the box HPE PPM, is configured to use UDP, as the base protocol for JGroups (multicast).  It is used for Cache synchronization and cluster monitoring (electing a schedule controller, etc.).  It is very important to ensure multicast is operational.  PPM has a built-in warning mechanism to inform Administrators of proper multicast function.  Messages will be logged to the serverLog.txt like

No multicast traffic has been heard from node Services on the MULTICAST_PORT port for over 15 minutes even though the node appears to be up. Please check your multicast routing, server.conf settings, and/or firewall settings.


There are multiple reasons these errors can occur.

1. Network Administrators do not allow UDP multicast required network configuration settings, per company policies.  Only under this circumstance, customers should consider switching to TCP as the Transport Protocol.

 If a message below is issued by your PPM Application server seen after starting:

No multicast traffic has been heard from node Services on the MULTICAST_PORT port for over 15 minutes even though the node appears to be up. Please check your multicast routing, server.conf settings, and/or firewall settings.

You may need to work with your Network Administrator. 

For example:  In a VLAN, if the Network Administrator, cannot enable.

ip pim sparse-mode

You can asked them for the below output of the below commands, to verify:

Sh run int vl <vlannumber>
Or
Sh ip pim interface


Under this case see the administrators guide “Set JGroups channels in TCP mode”

You can set the two JGroups channels in TCP mode. To switch to TCP mode,  for example:
in server.conf
com.kintana.core.server.SERVER_NAME=machine1
com.kintana.core.server.KINTANA_SERVER_NAME=node11
com.kintana.core.server.MULTICAST_ENABLE_TCP=true
com.kintana.core.server.MULTICAST_TCP_CACHE_PORT=10777
com.kintana.core.server.MULTICAST_TCP_INTEGRITY_PORT=10778

@NODE
com.kintana.core.server.SERVER_NAME=machine2
com.kintana.core.server.KINTANA_SERVER_NAME=node22
com.kintana.core.server.MULTICAST_TCP_CACHE_PORT=10779
com.kintana.core.server.MULTICAST_TCP_INTEGRITY_PORT=10780


To summarize, if UDP requirements cannot be meet due to company policy and it is proven.  You may try to switch Transport Protocols and utilize TCP.

2. If Multicast errors come much later than

com.kintana.core.server.MULTICAST_WARNING_MINUTES 

The root cause, is typically not related to underlying Transport protocol.  For example: if after many days, multicast errors begin to be continually logged to the serverLog.txt.  A support case should be submitted, to identify the root cause.

Labels (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.