Problem Note 18925: Concurrent execution of SAS® Marketing Automation campaigns results in intermittent failures
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:
<weblogic-enterprise-bean>
<ejb-name&>TaskExecutorBean</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>MATaskRequest</destination-jndi-name>
<connection-factory-jndi-name>MAJMSQueueConnectionFactory
</connection-factory-jndi-name>
</message-driven-descriptor>
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
| SAS System | SAS Marketing Automation-Server | Microsoft Windows XP Professional | 4.4 | 5.3 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 4.4 | 5.3 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Standard Edition | 4.4 | 5.3 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 4.4 | 5.3 | | 9.2 TS2M0 |
| Microsoft Windows 2000 Server | 4.4 | 5.3 | | 9.2 TS2M0 |
| Microsoft Windows 2000 Professional | 4.4 | 5.3 | | 9.2 TS2M0 |
| Microsoft Windows 2000 Datacenter Server | 4.4 | 5.3 | | 9.2 TS2M0 |
| Microsoft Windows 2000 Advanced Server | 4.4 | 5.3 | | 9.2 TS2M0 |
| 64-bit Enabled Solaris | 4.4 | 5.3 | | 9.2 TS2M0 |
| Solaris | 4.4 | 5.3 | | 9.2 TS2M0 |
| AIX | 4.4 | 5.3 | | 9.2 TS2M0 |
| 64-bit Enabled AIX | 4.4 | 5.3 | | 9.2 TS2M0 |
| HP-UX IPF | 4.4 | 5.3 | | 9.2 TS2M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Topic: | System Administration ==> Servers
|
| Date Modified: | 2007-06-19 11:53:14 |
| Date Created: | 2006-11-07 12:09:11 |
