Pankaj Parashar

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.

Posts by Pankaj Parashar

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 twoclustering 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.

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle Cluster Verification

On top of J2EE clustering, LiveCycle is clustered using Gemfire Distributed Cache. In cluster deployments, it is important that all the members of a LiveCycle cluster are able to find each other so that they can keep their individual caches in synchronization with one another. LiveCycle Cluster is configured properly or not can be identified based on two key indicators. The following are the key indicators.

  • Clustered Scheduler Service
  • Gemfire Logs

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle Cluster – TCP based JBoss Clustering

- Pankaj Parashar, Lead Softweare Engineer @ Adobe

Adobe LiveCycle comes with pre-configured JBoss (Community Edition only) . The preconfigured JBoss has both standalone and cluster-enabled configurations. All cluster-enabled configurations are based on UDP by default. Various enterprise organizations have very restrictive network policy and don’t allow multicasting in their networks. For such organizations, TCP based clustering is recommended option. JBoss instances belonging to different subnets require TCP based clustering only. In this article, we will go through detailed instructions to configure TCP based JBoss cluster. These instructions are applicable for both preconfigured JBoss and downloaded JBoss (Version 5.1 only).

The Following are the detailed instructions for TCP Clustering:

---

Read the complete post at Adobe LiveCycle Blog.

Windows Service For TCP Locator

- Pankaj Parashar, Lead Software Engineer @ Adobe

In most Windows server environments, users want software running as Windows services that are configured to auto-start and auto-stop on Windows start and stop. So far the LiveCycle provided TCP Locator is started using startlocator.bat script on the Windows environment. There is no inbuilt mechanism to start TCP Locator as a Windows service. However, there are various free tools available for creating Windows service for Java Applications. YAJSW (Yet Another Java Service Wrapper) is one such tool that wraps a Java process and runs it as a Windows service. YAJSW is an LGPL licensed tool.

---

Read the complate post at Adobe LiveCycle Blog.

JBoss Cluster Discarding Messages

- Pankaj Parashar, Lead Software Engineer @ Adobe

Sometimes while running LiveCycle on JBoss Cluster, you may see the following log messages appearing in server logs. WARN [org.jgroups.protocols.UDP] discarded message from different group “DefaultPartition” (our group is “LIVECYCLE-CLUSTER”). Sender was 10.56.78.90:54356

---

Read the complete post at Adobe LiveCycle Blog.

Pankaj Parashar's RSS Feed
Go to Top