Posts tagged "LiveCycle WebSphere Cluster"

The WebSphere server hangs while shutting down the WebSphere Cluster

When a user attempts to shut down WebSphere Cluster on which LiveCycle is deployed, the WebSphere server hangs occasionally and the following error message appears in the log:

000002f5 SystemOut     O cache has closed down , no further access allowed !,  exception caught in inserting  data in cache : CLUSTER_INVALIDATION_CACHE key: GLOBAL_PREFERENCES_UPDATE_TIMESTAMP_KEY value : null exception :com.adobe.livecycle.cache.CacheActionException: Cache container closed; normal during shutdown, error during runtime – Error on GET action for cache Replicated:CLUSTER_INVALIDATION_CACHE
 
000002f5 SystemOut     O  exception caught in inserting  data in cache : CLUSTER_INVALIDATION_CACHE key: GLOBAL_PREFERENCES_UPDATE_TIMESTAMP_KEY value : null exception :com.adobe.livecycle.cache.CacheActionException: Cache container closed; normal during shutdown, error during runtime – Error on GET action for cache Replicated:CLUSTER_INVALIDATION_CACHE

Reason

This error occurs because a child thread of the cache disconnect routine is hanging and therefore the servers do not respond to the shutdown command from the WebSphere Administration Console.


Solution

To stop the LiveCycle ES servers from the WebSphere Administration Console successfully:

  1. Log in to the WebSphere Administrative Console and, in the navigation tree, click Servers > Application servers and then, in the right pane, click the server name.
  2. Under Server Infrastructure, click Java and Process Management > Process Definition.
  3. Under Additional Properties, click Java Virtual Machine and add or configure following JVM argument:-Dadobe.cache.controlled-shutdown-disabled=true
  4. Click Apply.
  5. Click OK and then click save directly to the master configuration.
  6. Repeat steps 1-6 on each node of the cluster.
  7. Restart the cluster.

Now, the WebSphere server shuts down successfully.