Legacy Knowledge Base
Published Sep. 10, 2025

Several JGroups messages related to "Accept view MergeView" are appearing in a clustered node

Written By

Brian Suh

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Liferay's Cluster Link cache replication makes use of JGroups. There are instances when several JGroups messages related to "Accept view MergeView" are appearing while the cluster is running.

Environment

  • Liferay DXP 7.1
  • Liferay DXP 7.0
  • Liferay Portal 6.x

Resolution

  • An explanation of MergeView From JGroups MergeView Class Javadoc documentation:
    • Whenever a group splits into subgroups, e.g., due to a network partition, and later the subgroups merge back together, a MergeView instead of a View will be received by the application. The MergeView class is a subclass of View and contains an additional instance variable: the list of views that were merged. For example, if the group denoted by view V1:(p,q,r,s,t) splits into subgroups V2:(p,q,r) and V2:(s,t), the merged view might be V3:(p,q,r,s,t). In this case, the MergeView would contain a list of 2 views: V2:(p,q,r) and V2:(s,t).

    • From a practical perspective, please ensure that the clustered environment's network is stable and monitor for any changes.
Did this article resolve your issue ?

Legacy Knowledge Base