Errors occur when the session auditor does not find a remote id when updating the cache in SAS® Customer Intelligence Studio 6.6


In SAS Customer Intelligence Studio 6.6, the following error might occur every minute in the SASCustIntelCore6.6.log from the session manager:

ERROR [Thread-73] [] [] com.sas.analytics.crm.audit.AuditManager - Problem running audit: Push session data into shared cache once a minute.
java.lang.NullPointerException: key cannot be null
    at com.gemstone.gemfire.internal.cache.LocalRegion.validateKey
(LocalRegion.java:3155)
    at com.gemstone.gemfire.internal.cache.LocalRegion.validateArguments
(LocalRegion.java:3146)
    at com.gemstone.gemfire.internal.cache.LocalRegion.newUpdateEntryEvent
(LocalRegion.java:1620)
    at com.gemstone.gemfire.internal.cache.LocalRegion.put
(LocalRegion.java:1581)
    at com.gemstone.gemfire.internal.cache.AbstractRegion.put
(AbstractRegion.java:327)
    at com.sas.ci.services.common.cache.CISharedCacheImpl.put
(CISharedCacheImpl.java:57)
    at com.sas.ci.services.common.cache.CISharedCacheImpl.put
(CISharedCacheImpl.java:23)
    at com.sas.analytics.crm.security.ejb.SecurityManagerBean.pushSessionListItems
(SecurityManagerBean.java:911)
    at com.sas.analytics.crm.security.audit.PushSessionData.runAudit
(PushSessionData.java:22)
    at com.sas.analytics.crm.audit.AuditManager.prioritizeAndRunAudits
(AuditManager.java:88)
    at com.sas.analytics.crm.audit.AuditManager.runAudits
(AuditManager.java:37)
    at com.sas.analytics.crm.custdata.datapattern.DataPatternManager.runAudit
(DataPatternManager.java:1920)
    at com.sas.analytics.crm.webservices.ExternalAuditTask.run
(ExternalAuditTask.java:40)

This error comes from the session auditor when the remote ID that is used is null. The session auditor expects the remote ID to be available when updating the cache.

The auditor reads all sessions, and it is likely that the session was disconnected or no longer in use. The auditor will reset after the next SASServer6_1 restart.

If you have a single middle-tier configuration (not distributed), this should not impact functionality. It will add only the messages in the log until the next SASServer6_1 restart.

If you are using a distributed SASServer6_1 server, open a case with SAS Technical Support and share ALL SASCustIntelCore6.6.log files. 

These log files reside in the SAS-configuration-directory/Lev1/Web/Logs/SASServer6_1/ directory on the middle-tier machines.

This error message will not occur in the next release of SAS Customer Intelligence Studio.