Under some circumstances, background session IDs might become lost. This might happen when you execute campaign groups either via SAS^® Marketing Automation Launcher (sasmalauncher) or when you click Execute Now in SAS Customer Intelligence Studio. This problem might also happen when you leave SAS Customer Intelligence Studio sessions open for a long amount of time with no interaction.

When this problem occurs, the following message appears in the SASCustIntlCore6.x log:

In addition, the following error appears later in the SASCustIntelCore6.x log:

You might also see this error in the SASCustIntelCore6.x log:

There is no solid rule with regard to when the error occurs because the background execution thread is used for all campaigns, campaign groups, and SAS Marketing Automation metadata generation. The error is completely related to timing.

As a workaround for this problem, you need to enable the following Java argument:

When this argument is enabled, Java keeps the background session ID active.

To enable the Java argument in Microsoft Windows operating environments (where servers are started as Windows services):

1. Navigate to the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory and open the wrapper.conf file.
2. Add the new argument to the wrapper.conf file, as shown below:
   
   wrapper.java.additional.XX=-Dsas.ci.ma.sharedsid.disable

   In this argument, XX represents the next number in the sequence that already exists in the file. For the new argument, modify XX to be the next number in that sequence.

To enable the argument in Linux or other UNIX operating environments:

1. Navigate to the directory that contains the setenv.sh file. This file is typically located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory.
2. Add the highlighted argument to the setenv.sh file, as shown below:
   
   JVM_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,address=8003,server=y,suspend=n -Xmx4096m -Xss256k -Xms1024m -XX:PermSize=768m -XX:MaxPermSize=1280m -d64 -XX:NewRatio=8 -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:+DisableExplicitGC -XX:+CMSIncrementalMode -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -XX:ReservedCodeCacheSize=96m -Djava.awt.headless=true -Dcom.sas.services.logging.disableRemoteLogging=true -Dcom.sas.log.config.ignoreContextClassLoader=true -Dsas.svcs.http.max.connections=512 -Dsas.ci.ma.sharedsid.disable=true”

   Note: This SAS Note previously advised that you use the Java argument -Dsas.ci.debug.perUserSession.forceUseSourceSession. Because of performance issues with this Java argument, SAS Technical Support now advises that you use the argument that is highlighted above instead.

3. After you add the argument, restart the SASServer6_1 web application server so that the setting can take effect.

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

Note: After you apply the hot fix, the Java argument that you add in the workaround is no longer needed and should be disabled.

Operating System and Release Information

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

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