In a multi-node implementation of CA Service Catalog, one of the nodes is causing high CPU usage on the backend SQL MDB database
CA Service Catalog 17.3 and 17.4
There were multiple requests that are stuck in the ActiveMQ queue and it is suspected that these are causing high DB load since once the node is powered on trying to process all these requests at once.
Remove ActiveMQ materials from affected CA Service Catalog server
Try this during after hours or low time of production:
1. Take a backup of the jms-data folder on the problematic CA Service Catalog node (location is the CA Service Catalog install directory)
2. Once you have a backup, delete the entire contents of the jms-data folder
3. Restart the CA Service Catalog service