↓ Skip to main content
Milan’s Blog

Troubleshooting HCL Connections Docs Autopublishing: Resolving Message Store Corruption

·355 words·2 mins· loading · loading ·
Connections Docs Connections Hcl-Connections Hcl-Connections-Docs
Table of Contents

In a HCL Connections environment featuring HCL Connections Docs applications (including Docs Editor and Docs Proxy), I encountered an issue where the autopublishing feature was not functioning as expected. This feature is handy and adds to a good user experience, so it’s malfunction required immediate investigation.

Troubleshooting
#

Upon reviewing the HCL Connections Docs application logs, the following critical errors were identified:

000000a3 SibMessage    E   [IBMDocsBus:DocsCluster.000-IBMDocsBus] CWSIS1561E: The messaging engine's unique id does not match that found in the file store. ME_UUID=449029D40FBC38FE, ME_UUID(FS)=3D441AFD336F8019 
000000a3 SibMessage    E   [IBMDocsBus:DocsCluster.000-IBMDocsBus] CWSIS1567E: Messaging engine DocsCluster.000-IBMDocsBus cannot obtain the lock on its file store, which ensures it has exclusive access to the data. 
000000a3 SibMessage    E   [IBMDocsBus:DocsCluster.000-IBMDocsBus] CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.TransactionException: CWSIS1099E: An unexpected exception has occurred. Exception: com.ibm.ws.sib.msgstore.MessageStoreUnavailableException: Operation not possible as MessageStore is unavailable!

These error messages, indicate a corruption of the HCL Connections Docs application Message Stores. At this point, this was a probable cause for the autopublishing malfunction.

Solution
#

To resolve the issue, the Docs Message Stores needed to be recreated. As an additional measure, I’ve also decided to delete the Docs Viewer Message Stores to ensure a clean state for debugging, should the issue persist.

Follow these steps to recreate the message stores:

  1. Stop all HCL Connections Docs Application Servers.
  2. Optional but recommended - Backup any files before you delete them.
  3. Delete the Message Stores from the Docs Application shared storage. Typically found at the following locations:
<shared_storage_path>/docs/dataStore/Log
<shared_storage_path>/docs/dataStore/PermanentStore
<shared_storage_path>/docs/dataStore/TemporaryStore

<shared_storage_path>/viewer/dataStore/Log
<shared_storage_path>/viewer/dataStore/PermanentStore
<shared_storage_path>/viewer/dataStore/TemporaryStore
  1. Start all HCL Connections Docs Application Servers again.

Verfication
#

After the HCL Connections Docs applications have successfully restarted, it is crucial to verify that the Message Stores have been automaticaly recreated by the applications in the respective directories.

Outcome
#

Following these steps, the autopublishing feature started working as intended.

Additional Insight
#

It’s important to note that issues like Mesasge Store corruption often stem from underlying infrastructure problems such as:

  • Network outages
  • Operating System Crashes
  • Storage issues
  • etc.

Therefore, after encountering such problems, you shoud thoroughly inspect your environment for any recurring instabilities that could lead to similiar issues in the future.