LiveCycle – Application Server Clustering Verification

When running Adobe LiveCycle in cluster mode, it is important to verify that the cluster is configured and started successfully. LiveCycle deployment has has two clustering layers

  • Application Server Clustering
  • LiveCycle Clustering

LiveCycle runs on J2EE stack. J2EE level clustering should be configured as mentioned in LiveCycle cluster documentation. In this article we will go through each application server and based on logs determine if the clustering is successful or not, LiveCycle Clustering is described in the article – LiveCycle Cluster Verification.

JBoss

Check server logs of the JBoss node which is started first, you find the following messages (For UDP based Clustering).

2011-10-19 13:55:14,788 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (main) Initializing partition DefaultPartition

2011-10-19 13:55:14,913 INFO  [STDOUT] (JBoss System Threads(1)-3) ———————————————————GMS: address is 192.168.2.3:55200 (cluster=DefaultPartition)———————————————————

2011-10-19 13:55:15,147 INFO  [STDOUT] (main) ———————————————————GMS: address is 192.168.2.3:55200 (cluster=DefaultPartition-HAPartitionCache)———————————————————

2011-10-19 13:55:16,972 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (JBoss System Threads(1)-3) Number of cluster members: 1

2011-10-19 13:55:16,972 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (JBoss System Threads(1)-3) Other members: 0

2011-10-19 13:55:17,175 INFO  [org.jboss.cache.RPCManagerImpl] (main) Received new cluster view: [192.168.2.3:55200|0] [192.168.2.3:55200]

Note: You notice that initially there is only one member in the cluster. Here partition name is DefaultPartition which is default one. The name of partition depends on the value of jvm argument -Djboss.partition.name.

When other nodes join the first node following messages appear.

2011-10-19 13:55:18,501 INFO  [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] (Incoming-11,192.168.2.3:55200) New cluster view for partition DefaultPartition (id: 1, delta: 1) : [192.168.2.3:1099, 192.168.2.4:1099]

2011-10-19 13:55:18,501 INFO  [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] (AsynchViewChangeHandler Thread) I am (192.168.2.3:1099) received membershipChanged event:

2011-10-19 13:55:18,501 INFO  [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] (AsynchViewChangeHandler Thread) Dead members: 0 ([])

2011-10-19 13:55:18,501 INFO  [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] (AsynchViewChangeHandler Thread) New Members : 1 ([192.168.2.4:1099])

2011-10-19 13:55:18,501 INFO  [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] (AsynchViewChangeHandler Thread) All Members : 2 ([192.168.2.3:1099, 192.168.2.4:1099])

Note: Here you can see that membershipChanged event is triggered and count for New Members and All Members is updated based on the number of nodes joining the cluster.

Check server logs of the JBoss nodes which are previously started. You find the following messages.

2011-10-19 13:55:15,520 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (main) Initializing partition DefaultPartition

2011-10-19 13:55:15,692 INFO  [STDOUT] (JBoss System Threads(1)-3) ———————————————————GMS: address is 192.168.2.4:55200 (cluster=DefaultPartition)———————————————————

2011-10-19 13:55:15,910 INFO  [org.jboss.cache.jmx.PlatformMBeanServerRegistration] (main) JBossCache MBeans were successfully registered to the platform mbean server.

2011-10-19 13:55:16,019 INFO  [STDOUT] (main)

———————————————————GMS: address is 192.168.2.4:55200 (cluster=DefaultPartition-HAPartitionCache)———————————————————

2011-10-19 13:55:17,345 INFO  [org.jboss.cache.RPCManagerImpl] (main) Received new cluster view: [192.168.2.3:55200|1] [192.168.2.3:55200, 192.168.2.4:55200]

2011-10-19 13:55:17,423 INFO  [org.jboss.cache.statetransfer.LegacyStateTransferIntegrator] (Incoming-4,192.168.2.4:55200) Using version 4096

2011-10-19 13:55:17,439 INFO  [org.jboss.cache.RPCManagerImpl] (main) Cache local address is 192.168.2.4:55200

2011-10-19 13:55:17,455 INFO  [org.jboss.cache.RPCManagerImpl] (main) state was retrieved successfully (in 1.47 seconds)

2011-10-19 13:55:17,470 INFO  [org.jboss.cache.factories.ComponentRegistry] (main) JBoss Cache version: JBossCache ‘Malagueta’ 3.2.5.GA

2011-10-19 13:55:18,313 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (JBoss System Threads(1)-3) Number of cluster members: 2

2011-10-19 13:55:18,313 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (JBoss System Threads(1)-3) Other members: 1 

Weblogic

For WebLogic clustering, check the log file for each server in the cluster. Each server node synchronizes to the other nodes of the cluster. Each time a node is added (or started); other nodes of the cluster add the node to their cluster view.

<BEA-000138> <Listening for announcements from cluster LC_CLUSTER on 239.192.0.0:45607.>

####<Oct 10, 2011 4:22:18 PM IST> <Notice> <Cluster> <nodeB> <nodeB> <[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1318243938775> <BEA-000133> <Waiting to synchronize with other running members of LC_CLUSTER.>

####<Oct 10, 2011 4:55:01 PM IST> <Info> <Cluster> <nodeA> <nodeA> <[STANDBY] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1318245901625> <BEA-000111> <Adding nodeB with ID 2263843765604588296S:nodeB:[8001,8001,-1,-1,-1,-1,-1]:lc_cluster:nodeB to cluster: LC_CLUSTER view.>

####<Oct 10, 2011 5:07:56 PM IST> <Notice> <Cluster> <nodeA> <nodeA> <[ACTIVE] ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1318246676251> <BEA-000102> <Joining cluster LC_CLUSTER on 239.192.0.0:45607>

####<Oct 10, 2011 5:07:57 PM IST> <Info> <Cluster> <nodeA> <nodeA> <[STANDBY] ExecuteThread: ‘4’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1318246677940> <BEA-000128> <Updating 2263843765604588296S:nodeB:[8001,8001,-1,-1,-1,-1,-1]:lc_cluster:nodeB in the cluster.>

WebSphere

For WebSphere clustering, all server nodes, node agents, and deployment manager communicate to each other, as a part of a core group member. If you choose cluster members to be part of the default core group or a custom core group, you can see the following messages showing that all these members of the core group forming a group and connecting to its member.

[10/19/11 9:48:36:841 IST] 00000000 DCSPluginImpl I   HMGR0001I: The DCS Core Stack transport has been started for core group DefaultCoreGroup. There are 5 members.

[10/19/11 9:48:37:012 IST] 00000010 MbuRmmAdapter I   DCSV1032I: DCS Stack DefaultCoreGroup at Member nodeACell01\nodeBNode01\nodeB: Connected a defined member nodeACell01\nodeBNode01\nodeagent.

[10/19/11 9:48:37:044 IST] 00000010 MbuRmmAdapter I   DCSV1032I: DCS Stack DefaultCoreGroup at Member nodeACell01\nodeBNode01\nodeB: Connected a defined member nodeACell01\nodeACellManager01\dmgr.

[10/19/11 9:48:37:153 IST] 00000010 MbuRmmAdapter I   DCSV1032I: DCS Stack DefaultCoreGroup at Member nodeACell01\nodeBNode01\nodeB: Connected a defined member nodeACell01\nodeANode01\nodeA.

Note: Total number of members includes deployment manager, server nodes, and their node agents. So if you have a topology of a two-node cluster with a deployment manager, there are 5 members in the group.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.5/10 (2 votes cast)
LiveCycle - Application Server Clustering Verification, 9.5 out of 10 based on 2 ratings

About Pankaj Parashar

Pankaj Parashar is a Lead Software Engineer at Adobe Systems. He is working for Adobe LiveCycle Enterprise Suite. He looks after cluster deployments and LiveCycle SDK testing. His interests include programming, cloud, big data and analytics. He is based out of Noida, India.
This entry was posted in Adobe LiveCycle ES3 and tagged , , , , . Bookmark the permalink.

One Response to LiveCycle – Application Server Clustering Verification

  1. blog site says:

    Ik vind dit blog.Very prachtige informatie is te vinden op de website blog. “De kwaliteit van een organisatie kan nooit hoger zijn dan de kwaliteit van de geesten die het goed te maken.