SAS Real-Time Decision Manager enables you to use custom DS2 code in order to add functionality to campaigns. The DS2 code is executed on an underlying SAS Federation Server that is installed and configured as part of SAS Real-Time Decision Manager. When you use DS2 code heavily in your campaigns, you might see intermittent periods in which response time is unacceptably high. This problem is more likely to occur if the custom code makes many SQL calls. Restarting SAS Real-Time Decision Manager returns response time to normal, but does not prevent eventual recurrence of the problem.  

There are no easily detectable errors or warnings that are specific to this problem. Memory usage does not become unusually high, nor does CPU usage.  In fact, there are no obvious resource constraints. In a Java thread dump for the SAS Federation Server, like the one shown below, you can see that an unexpectedly large number of threads (sometimes > 200) are in a state of waiting:

The Decision Services log might also contain messages that the connections to the SAS Federation Server are killed and restarted more often than expected because of timeouts in DS2 activity execution.

The underlying memory management for DS2 objects can require too much time as the number of DS2 objects grows. Making multiple unparameterized SQLSTMT calls can cause particular strain.

You can alleviate this problem by adding more SAS Federation Servers to your architecture. However, modifying SAS Federation Server configuration or adding resources to existing SAS Federation Servers does not resolve the issue.

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

Post Hot Fix Instructions

In addition to installing the hot fix, you must also enable pool caching by setting the SKM_POOL_CACHE=1 environment variable:

1. Stop SAS Federation Server.
2. Set the SKM_POOL_CACHE=1 environment variable.
   Note: For Linux, you use:  export SKM_POOL_CACHE=1
3. Restart SAS Federation Server

Operating System and Release Information

A fix for this issue for SAS Federation Server 4.2 is available at:

A fix for this issue for SAS Federation Server 4.1_M1 is available at: