Symptom
Hybris JGroups cluster nodes take long time to start, somtimes up to 15 minutes or longer, with mutliple warnings in the log.
Warnings such as.
WARN [localhost-startStop-1] [GMS] hybrisnode-1: JOIN(hybrisnode-1) sent to hybrisnode-1 timed out (after 3000 ms), on try 1
In he database, you will find stale JGroup node entries in the JGROUPSPING table and they will start to accumulate.
Read more...
Environment
-
Hybris Commerce Suite with version below 1811.0
- JGroup version below 4.0.5
- At least 2 nodes set up in a JGroup TCP cluster. One node acting as a coordinator and one as a regular node.
Product
SAP Hybris Commerce 1808 ; SAP Hybris Commerce 6.0 ; SAP Hybris Commerce 6.1 ; SAP Hybris Commerce 6.2 ; SAP Hybris Commerce 6.3 ; SAP Hybris Commerce 6.4 ; SAP Hybris Commerce 6.5 ; SAP Hybris Commerce 6.6 ; SAP Hybris Commerce 6.7 ; SAP hybris Commerce 5.0.3 ; SAP hybris Commerce 5.0.4 ; SAP hybris Commerce 5.7 ; SAP hybris Commerce Suite 5.2 ; SAP hybris Commerce Suite 5.3 ; SAP hybris Commerce Suite 5.4 ; SAP hybris Commerce Suite 5.5 ; SAP hybris Commerce Suite 5.5-1 ; SAP hybris Commerce Suite 5.6 ; hybris Commerce Suite 4.4 ; hybris Commerce Suite 4.5 ; hybris Commerce Suite 4.6 ; hybris Commerce Suite 4.7 ; hybris Commerce Suite 4.8 ; hybris Commerce Suite 5.0 ; hybris Commerce Suite 5.1 ; hybris Commerce Suite 5.1.1
Keywords
jgroups, jgroup, jdbc_ping, jdbc ping, jgroup cluster, cluster, startup, slow, jgroups tcp , KBA , CEC-COM-CPS , SAP Commerce , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.