Purge ActiveMQ Folders in ITPAM

Products

• CA Process Automation Base
• Process Automation Manager

Issue/Introduction

ActiveMQ database corruption or excessive log buildup can prevent the Orchestrator from starting correctly.

For example, in the <PAM Installation Folder>\wildfly\standalone\log\c2o.log file you might see:

ERROR [com.optinuity.c2o.c2oserver.ServerManager] [      Thread-13] Unable to start ActiveMQ or it has been stopped...

Environment

Process Automation v4.3.x and v4.4.x

Resolution

To resolve this problem:

1. Stop the Orchestrator service.
2. Verify no Java.exe processes are still running on the server.
3. Navigate to <PAM Installation Folder>\activemq.
4. Rename the <PAM Installation Folder>\activemq\activemq-data folder (e.g., to activemq-data.old).
5. Start the Orchestrator service. The ActiveMQ database will be recreated automatically.

Additional Information

Note: After following the steps, the 1st restart of the Orchestrator service might take a little bit longer to fully initialize and ITAPM be accessible.

See also: ActiveMQ not starting after an abnormal stop of server