TechNote

Unable to stop clustered LiveCycle ES server from WebSphere Administration Console

Issue

---

The following error occurs when you attempt to stop clustered LiveCycle ES servers from the WebSphere Administration Console:

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
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 stop command from the WebSphere Administration Console.

Solution

---

To stop the LiveCycle ES servers from the WebSphere Administration Console successfully, do not invoke the disconnect on the cache and make the following modifications to disable either UDP multicast or TCP locator.

1. Stop and undeploy LiveCycle ES.
2. Stop the WebSphere server.
3. Delete the contents of the WebSphere logs directory (for example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs).
   

   Note: Save copies of the logs from each node, if required.

4. Unpack the adobe-core-websphere.ear file.

5. Open the application.xml file in an editor, and comment out the CacheController module:
   
   <!--module id="CacheController">


   <web>
<web-uri>adobe-cache-controller.war</web-uri>
<context-root>/cache-controller</context-root>

</web>


   </module-->

6. Save and close the file and repackage the adobe-core-websphere.ear file.
7. Redeploy and start LiveCycle ES.

You should now be able to stop the server from the WebSphere Administration Console.

Search Support

---