Symptoms:
SOI console stops publishing the alerts from the connectors.
In the SOI manager server, if you find the following errors in \SOI\log\ifw.log.
Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://<SOI-manager-host>:61616. Reason: java.net.ConnectException: Connection refused: connect at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286)
at org.apache.activemq.ActiveMQConnectionFactory.createTopicConnection(ActiveMQConnectionFactory.java:215)
at com.ca.sam.ifw.api.jms.JMSImpl.msgBusCreateTopicConnection(JMSImpl.java:390)
Release: SOI 3.1, 3.2, 3.3, 4.0, 4.1, 4.2
By default, there are four files in SOI\tomcat\webapps\activemq-web\activemq-data on the SOI manager. There are some corruptions in this directory to cause SOI manager stop publishing the alerts.