Campaigns in SAS Marketing Automation might intermittently fail or stop responding for no apparent reason. This problem occurs because concurrent tasks clash. You should be able to avoid the problem by specifying 1 as the maximum number of concurrent processes per diagram on the Environment tab in the SAS Marketing Automation Administrative Tools Plug-In of SAS^® Management Console. However, because of another issue (see SAS Note 18901), this workaround does not work.

The only way to work around this issue if it occurs is to limit the number of message beans in the application server.

For WebLogic, you need to change the MAX-BEANS-IN-FREE-POOL setting to 1 in the WEBLOGIC-EJB.JAR deployment descriptor and then redeploy the .EAR file:

For WebSphere, you need to set the

• maximum number of sessions to 1:
  Servers > Application Servers > server1 > Message Listener Service > Listener Ports > Task Executor Bean Port > Maximum sessions
• maximum number of connections to 1:
  Resources > Websphere JMS Provider > WebSphere Queue Connection Factories > MAJMSQueueConnectionFactory > Session Pools > Max Connections

Select the Hot Fix tab in this note to access the hot fix for this issue.

Once you have applied this hot fix you must bring these settings back up to their recommended values.

A best practice is to set them equal to the maximum number of concurrent processes per diagram defined on the SAS Management Console Marketing Automation Administration plug-in Environment tab.

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 4.4 is available at: