The ActiveMQ component in SOI will stop working if a journal file is missing.
In the soimgr.log, you will see the following trype of error messages...
ERROR [ActiveMQ Transport: tcp:///*.*.*.*:53839] cursors.AbstractStoreCursor.fillBatch(264) - Failed to fill batch
java.io.IOException: Could not locate data file C:\Program Files (x86)\soi\tomcat\webapps\activemq-web\activemq-data\db-9552.log
ERROR [localhost-startStop-1] broker.BrokerService.start(528) - Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: Detected missing/corrupt journal files. 1 messages affected.
java.io.IOException: Detected missing/corrupt journal files. 1 messages affected.
This is caused by the configuration setting in the <SOI_HOME>\tomcat\webapps\activemq-web\WEB-INF\caifwmq.xml
<persistenceAdapter>
<!--<amqPersistenceAdapter syncOnWrite="false" directory="${activemq.base}/data" maxFileLength="32 mb"/>-->
<kahaDB directory="C:\Program Files (x86)\CA\SOI\tomcat\webapps\activemq-web\activemq-data" journalMaxFileLength="100kb" cleanupInterval="5000"/>
</persistenceAdapter>
You can manually fix this by editing <SOI_HOME>\tomcat\webapps\activemq-web\WEB-INF\caifwmq.xml and change and add the following
This is caused by the configuration setting in the <SOI_HOME>\tomcat\webapps\activemq-web\WEB-INF\caifwmq.xml
<persistenceAdapter>
<!--<amqPersistenceAdapter syncOnWrite="false" directory="${activemq.base}/data" maxFileLength="32 mb"/>-->
<kahaDB directory="C:\Program Files (x86)\CA\SOI\tomcat\webapps\activemq-web\activemq-data" journalMaxFileLength="32mb" cleanupInterval="5000" ignoreMissingJournalfiles="true"/>
</persistenceAdapter>
After saving the file, you will need to delete all the files in \soi\tomcat\webapps\activemq-web\activemq-data\ folder and recycle the CA SAM Application Server service.
NOTE: If you don't see that section in your caifwmq.xml file, then your SOI manager is not effected by this configuration problem.
The SOI SE team is aware of this problem and will be providing a fix sometime this month.