When you execute a campaign by using either the scheduler or the Execute now option in SAS Customer Intelligence Studio, the campaign does not seem to finish.

If you schedule more than one campaign, the first campaign starts to execute. However, because it seems to not finish, all other subsequent scheduled campaigns do not start. They do not start because they are waiting for the first one to finish.

The same problem occurs when you execute the campaign interactively in SAS Customer Intelligence Studio. When you log off and log back on to SAS Customer Intelligence Studio, the campaign indicates that it has finished. Also, the MALauncher and the SASCustIntelCore6.3 log show that the campaign finished execution.

You also might see that email notifications are not sent out.

This problem can occur when 100% of the storage is used by Apache ActiveMQ (Java Messaging Service). When all of the storage is used, ActiveMQ might stop processing.

If you look at the activemq log (located on your middle-tier machine in the SAS-configuration-directory\Lev1\Web\activemq\data directory), you might see the following messages:

To check the status of the JMS broker, do one of the following:

• In a UNIX operating environment: Run the command-line script /sas/config/Lev1/Web/activemq/bin/activemq status.
• In a Windows operating environment: Check the status of the running JMS broker Windows Service that is called SAS [Config-Lev1] JMS Broker on port 61616.

To verify whether the problem is a result of ActiveMQ using all of the storage space:

1. Enable the ActiveMQ web console by adding the following line to the activemq.xml file that is located in SAS-configuration-directory\Lev1\Web\activemq\conf. Add this line at the end of the file, before the final </beans> element).
   </systemUsage> <import resource="file:///${activemq.base}/conf/jetty.xml"/>
2. Restart ActiveMQ (the service is named JMS Broker) and access the web console with this URL via http://localhost:8161/admin.
3. Check the home page to see whether the value for Store Percent Used is 100%. If it is, increase the storage size for ActiveMQ and restart the middle tier.

   To increase the storage size, edit the activemq.xml file again and change storeUsage from 20 GB to 30 GB as shown below:

   <systemUsage>
      <systemUsage>
         <memoryUsage>
            <memoryUsage limit="256 mb"/> 
         </memoryUsage>
         <storeUsage>
            <storeUsage limit="30 gb"/>
         </storeUsage>
         <tempUsage>
            <tempUsage limit="5 gb"/>
         </tempUsage>
      </systemUsage>
4. After you increase the storage size, verify the percentage of storage that is used.

You can also find useful information for solving this problem in SAS Note 52315: "Increasing numbers of Apache ActiveMQ journal log files in certain SAS^® 9.4 Enterprise BI and SAS^® Visual Analytics environments fill up disk space."

If you are using SAS^® 9.4M5 (TS1M5), contact SAS Technical Support for details about how to enable the ActiveMQ web console.

Operating System and Release Information