SUPPORT / SAMPLES & SAS NOTES
Problem Note 62502: Generating input data for a MOMA campaign group might fail in a clustered, middle-tier environment
 |  |  |  |  |
In SAS® Customer Intelligence Studio, the generation of input data might fail when you optimize a MOMA campaign group in a clustered middle-tier environment.
When the failure occurs, the following error message is displayed in the SASCustIntelCore6.x.log file:
2018-05-18 11:57:11,893 ERROR [CIAsyncExec-10][9c1ecf9a6d864fe8:1ff58ea0:16372895162:-60a5] [sasdemo] com.sas.analytics.crm.cm.CICampaignGroup - runOptimization():
MO is unable to optimize via MOMABridgeServiceInterface com.sas.ci.services.common.error.CIException: no queue defined for AsyncKeyImpl:SASServer6_1_.xxxx.xxx.xxx:2 on SASServer6_2_xxxx.xxx.xxx
MO is unable to optimize via MOMABridgeServiceInterface com.sas.ci.services.common.error.CIException: no queue defined for AsyncKeyImpl:SASServer6_1_.xxxx.xxx.xxx:2 on SASServer6_2_xxxx.xxx.xxx
At the same time, the following message is displayed in the SASMarketingOptimization6.x.log file:
2018-05-18 13:37:43,418 WARN [tomcat-http--4] [] [] org.springframework.remoting.support.RemoteInvocationTraceInterceptor - Processing of HttpInvokerServiceExporter remote call resulted in fatal exception:
com.sas.ci.services.common.plugins.bridge.MOMABridgeServiceInterface.getAsyncResult
com.sas.ci.services.common.error.CIException: no queue defined for AsyncKeyImpl: SASServer6_1_.xxxx.xxx.xxx:2 on SASServer6_2_xxxx.xxx.xxx
at com.sas.ci.services.common.communication.AsyncCommunicationServiceImpl.assertQueueNotNull(AsyncCommunicationServiceImpl.java:147)
com.sas.ci.services.common.plugins.bridge.MOMABridgeServiceInterface.getAsyncResult
com.sas.ci.services.common.error.CIException: no queue defined for AsyncKeyImpl: SASServer6_1_.xxxx.xxx.xxx:2 on SASServer6_2_xxxx.xxx.xxx
at com.sas.ci.services.common.communication.AsyncCommunicationServiceImpl.assertQueueNotNull(AsyncCommunicationServiceImpl.java:147)
Most likely, this problem occurs when the environment is under a heavy load with regard to the SAS® Web Server. In certain high-load circumstances, the SAS Web Server loses the session to the appropriate cluster node.
When this problem happens, the only solution is to restart the middle-tier environment.
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.5 | 6.6 | 9.4 TS1M6 | |
| 64-bit Enabled AIX | 6.5 | 6.6 | 9.4 TS1M6 | |||
| 64-bit Enabled Solaris | 6.5 | 6.6 | 9.4 TS1M6 | |||
| HP-UX IPF | 6.5 | 6.6 | 9.4 TS1M6 | |||
| Linux for x64 | 6.5 | 6.6 | 9.4 TS1M6 | |||
| Solaris for x64 | 6.5 | 6.6 | 9.4 TS1M6 | |||