After a server reboot the Tibco message queue appears to start but may be hung while recovering messages. We cannot connect with the admin account in order to clean up the queues.
MessageQueue]# tail /opt/CA/AccessControlServer/MessageQueue/tibco/log/ems.log
2022-05-08 09:51:52.523 SEVERE ERROR: No memory to create prop.
2022-05-08 09:51:52.530 SEVERE ERROR: No memory to create prop.
2022-05-08 09:51:52.536 SEVERE ERROR: No memory to create prop.
The message queues grew too large and appeared to be possibly corrupted during the failover startup. This grew large since 3 distribution servers were decommissioned but never removed from the /opt/CA/AccessControlServer/MessageQueue/tibco/cfgmgmt/ems/data/tibmsd.conf
Release : 12.8
Component : CA ControlMinder - Unix
If you cannot login to tibco to clear the queues using the purge command, you can
1. stop tibco (/etc/init.d/ca-acrptmq stop)
2. delete or rename all 3 of the database files in the datastore (async-msgs.db, meta.db, sync-msgs.db)
3. start tibco (/etc/init.d/ca-acrptmq stop)
note: this will delete all message data but will not clear any configurations.