What is Jgroups, How is it used, and How to Find Out if it is working correctly - An Overview (Doc ID 1041041.1)

Last updated on MAY 24, 2017

Applies to:

Oracle Knowledge - Version 8.1.2.1 to 8.6 [Release 8.1 to 8.6]
Information in this document applies to any platform.
Information in this document applies to any platform.

Symptoms

Currently OOTB IM uses the jGroups with the default multicasting address 230.0.0.1:9375 UDP messaging as the mechanism to sync-up the cached data across all IM instances (IM Console, infocenter and imws) within a given env (Dev, QA or Prod).  To avoid 'cross-contamination' of those multicasting UDP messages among the Dev, QA and Prod env (if they are all resided on the same subnet LAN), the IM instances should be configured to have UNIQUE jGroup identifiers per env (Dev, QA and Prod).  Typically, the OOTB jgroups settings are defined in the corresponding IM application/properties files like in the folders of <IM_HOME>/InfoManager/config/IMADMIN (for IM Console instance), IMWEBSERVICES (for IMWS instance) and <My IC repository refkey> (for IC instances).  This information is located in this KM article:

- How can I configure JGroups? What port does JGroups use? (Doc ID 1040700.1)

The product requires that jgroups be enabled for much of the communication between the components to happen.  Oracle does not support running without jgroups enabled.

Changes

Some common problems that you may see that can lead you to think jgroups is not working.

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