When you optimize MOMA input data in SAS Customer Intelligence Studio, you might see the following pop-up message:

At the same time, the following error is displayed in the SAS^® Marketing Optimization middle-tier log:

You will also see connection-reset issues in the middle-tier logs, as shown below:

SASCustIntelCore6.x.log:

SASMarketingOptimization6.x.log:

Almost 300 seconds after the last message above, the following message is generated:

Then, another 300 seconds after the last message above, the following message is generated:

You should have only one of these entries in the logs for a particular instance of generating or refreshing MOMA input data or for an optimization run for a campaign group. Once the HTTP/HTTPS time-out happens, the process is retried, which causes execution failures.

When the generation of MOMA input data fails and you submit a scenario for optimization, the following error is displayed in the SASMarketingOptimization6.x.log (middle tier):

These errors occur when a short HTTP/HTTPS time-out is set for the middle-tier web server. In this scenario, the HTTP/HTTPS connection might time out before the operation on the SAS Marketing Optimization side is complete.

To work around this issue, you need to increase the time-out setting for the HTTP/HTTPS connection.

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

Now that the hot fix is available, two new Java arguments are introduced that control how long and how many times the operation will retry. These new arguments have the following standard settings to complete the operation:

-sas.ci.momabridge.poll.timeout (default 60 seconds)

-sas.ci.momabridge.poll.maxloops (default 720, which means 12 hours) 

To change the default time-out setting, you need to add the following two new Java arguments to the wrapper.conf file (Microsoft Windows operating environments) or the setenv.sh file (UNIX and Linux operating environments):

-Dcom.sas.ci.momabridge.poll.timeout=60

-Dcom.sas.ci.momabridge.poll.maxloops=1440

Note: These two arguments are available only after you apply the hot fix that is found on the Hot Fix tab.

• Under Windows, the wrapper.conf file is available in the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory. In the wrapper.conf file, add the arguments as shown below:

wrapper.java.additional.XX=-Dcom.sas.ci.momabridge.poll.timeout=60  

wrapper.java.additional.XX=-Dcom.sas.ci.momabridge.poll.maxloops=1440

Note: In the wrapper.java.additional.XX property, XX specifies the next number in the sequence that already exists in the file. Modify XX to be the next number in that sequence.

• Under Linux and other UNIX operating environments, the setenv.sh file is located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory.

  Add the two arguments to the JAVA_OPTS= property, as shown below:

  JAVA_OPTS="$JAVA_OPTS -Dcom.sas.ci.momabridge.poll.timeout=60 -Dcom.sas.ci.momabridge.poll.maxloops=1440

After you add the arguments to the appropriate file for your operating system, restart the middle tier in order for the settings to take effect.

Operating System and Release Information

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

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

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