When you execute large SAS Marketing Optimization scenarios, SASServer6_1 might stop responding and fail with the following error shown in the server.log:

[LCDS]11/03/2014 17:42:27.729 [INFO] JMS consumer for JMS destination 'java:comp/env/jms/CIClientEvent' is stopping.
[LCDS]11/03/2014 17:42:27.729 [INFO] The corresponding MessageClient for JMS consumer for JMS destination 
   'java:comp/env/jms/CIClientEvent' is being invalidated
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space

At the same time, you might encounter this message in the SASMarketingOptimization6.3.log:

2014-11-03 17:42:27,768 ERROR [tomcat-http--19] [41643fecf267eb1a:1016332a:149728d2f03:-ded] [sasdemo] m.sas.analytics.mo.server.MetadataServer - Class:com.sas.analytics.mo.server.MetadataServer Method:getPublicObjectMetadataInterfacesForReadOnly Exception:Java heap space

Before the error occurs, CPU usage goes to 100% and the system becomes unresponsive to users. Memory use increases regardless of what users are doing in SAS Marketing Optimization (for example, uploading input data or running a scenario or optimization).

A problem was found in the SAS Marketing Optimization JMS messaging configuration for client communications where the time-to-live value for the message queue was set to 0. This was causing events to remain in the queue after consumption. This issue is particularly noticeable for customers with large-scenario objects.

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

Operating System and Release Information

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