When SAS^® Customer Intelligence is deployed on WebSphere, you might see the following errors in both the SAS Customer Intelligence macore and Web server systemout logs:

This error is reported because SAS Customer Intelligence caches queue connections and these are sometimes lost. The connections are automatically re-established, therefore, no failures occur, but the error is thrown to the logs.

A hot fix is available for this issue. It removes this error by disabling the caching of connections

Once the hot fix has been applied, you will need to change the JVM arguments for the SAS^® Marketing Automation core application to disable caching. If these arguments are not changed, then caching will not be disabled:

IBM Websphere

To set generic JVM arguments in WebSphere 5.1, do the following:

1. Log on to the Administration Console and navigate to:

   Application Servers ► server1 ► Process Definition ►

2. Add the following property to the executable arguments:

   -Dcom.sas.analytics.crm.task.cacheJMSConnection=false

3. Restart Websphere.

BEA Weblogic

To set generic JVM arguments in Weblogic 8.1, do the following:

1. Navigate to:

   C:\bea\user_projects\domains\mydomain (Windows)
   ....bea/user_projects/domains/mydomain (UNIX)

2. Edit the startweblogic.cmd file by adding the following property:

   set JAVA_OPTIONS=%JAVA_OPTIONS% -Dcom.sas.analytics.crm.task.cacheJMSConnection=false

3. If you are starting the SAS Managed Server in Weblogic from the Administration console, log on to the console.
4. Navigate through SASSolutions ► Servers ► SAS Managed Server, then select the Configuration ► Remote Start tabs.
5. Add the following to the arguments in the arguments field:

   -Dcom.sas.analytics.crm.task.cacheJMSConnection=false

6. Restart your SAS Managed Server.

Select 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 Automation 5.1 is available at: