Problem Note 58534: Errors are generated when scheduled campaigns fail to launch in SAS® Customer Intelligence
 |  |  |  |  |
When multiple SAS Customer Intelligence campaigns are scheduled to start simultaneously, some of those campaigns might not launch. No exit status values are returned from the campaign to the scheduling software. However, errors similar to the following appear in both the SASCustIntelCore log and the malauncher log (if you have the malauncher log enabled):
Errors that appear in the SASCustIntelCore log:
2016-01-20 01:52:08,499 WARN [tomcat-http--16] [] []
support.RemoteInvocationTraceInterceptor - Processing of
HttpInvokerServiceExporter remote call resulted in fatal exception:
com.sas.analytics.crm.ma.client.MAConfigInterface.getFolderTree
java.lang.ArrayIndexOutOfBoundsException: -1
at java.text.DigitList.fitsIntoLong(DigitList.java:229)
at java.text.DecimalFormat.parse(DecimalFormat.java:1314)
at
java.text.SimpleDateFormat.subParse(SimpleDateFormat.java:2086)
at java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1455)
at java.text.DateFormat.parse(DateFormat.java:355)
at
com.sas.analytics.crm.persistence.metadata.OMRFolderUtil.getFolderTreeDO(OMRFold
erUtil.java:423)
at
com.sas.analytics.crm.persistence.metadata.OMRFolderUtil.getFolderTreeDO(OMRFold
erUtil.java:439)
at
com.sas.analytics.crm.persistence.metadata.OMRFolderUtil.getFolderTreeDO(OMRFold
erUtil.java:439)
at
com.sas.analytics.crm.persistence.metadata.OMRFolderUtil.getFolderTreeDO(OMRFold
erUtil.java:439)
at
com.sas.analytics.crm.persistence.metadata.OMRFolderUtil.getOMRFolderInfoUsingFi
lter(OMRFolderUtil.java:1046)
at
com.sas.analytics.crm.persistence.metadata.OMRFolderUtil.getOMRFolderInfo(OMRFol
derUtil.java:316)
at
com.sas.analytics.crm.persistence.metadata.OMRFolderUtil.getFolderTree(OMRFolder
Util.java:164)
at
com.sas.analytics.crm.persistence.metadata.OMRFolderUtil.getFolderTree(OMRFolder
Util.java:181)
at
com.sas.analytics.crm.ma.ejb.MAConfigBean.getFolderTree(MAConfigBean.java:5206)
at sun.........................
Errors that appear in the MALauncher log:
2016-01-20 01:52:08,935: ...
ERROR Could not access HTTP invoker remote service at
[http://xxxx/ci63/remote/Launcher]; nested exception is
org.apache.commons.httpclient.HttpException: Did not receive successful HTTP
response: status code = 503, status message = [Service Temporarily Unavailable]
org.springframework.remoting.RemoteAccessException: Could not access HTTP
invoker remote service at [http://xxxx/ci63/remote/Launcher]; nested
exception is org.apache.commons.httpclient.HttpException: Did not receive
successful HTTP response: status code = 503, status message = [Service
Temporarily Unavailable]
at
org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHtt
pInvokerAccessException(HttpInvokerClientInterceptor.java:212)
at
org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(Htt
pInvokerClientInterceptor.java:145)
at
com.sas.svcs.remoting.client.SASClientTicketingProxy.invoke(SASClientTicketingPr
oxy.java:147)
at
com.sas.ci.services.common.remoting.CIServicesTicketingProxy.invoke(CIServicesTi
cketingProxy.java:98)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveM
ethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.j
ava:202)
at com.sun.proxy.$Proxy29.getStatus(Unknown Source)
at
com.sas.analytics.crm.ma.launcher.MALauncher.main(MALauncher.java:107)
Caused by: org.apache.commons.httpclient.HttpException: Did not receive
successful HTTP response: status code = 503, status message = [Service
Temporarily Unavailable]
at org..........................
To avoid this issue, do not schedule multiple campaigns to start simultaneously.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Customer Intelligence Core Mid-Tier | Microsoft® Windows® for x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
| 64-bit Enabled AIX | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 | ||
| 64-bit Enabled Solaris | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 | ||
| HP-UX IPF | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 | ||
| Linux for x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 | ||
| Solaris for x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 | ||
A fix for this issue for SAS Marketing Automation 6.3 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/R60.html#58534| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2016-10-31 16:20:28 |
| Date Created: | 2016-06-29 15:39:27 |