Problem Note 59634: Executing several sasmalauncher sessions in a clustered, middle-tier environment might fail
 |  |  |  |  |
When you execute several sasmalauncher sessions in a clustered, middle-tier environment, the sessions might fail. When a failure occurs, the following error message is generated in the SASCustIntelCore6.x or sasmalauncher.log:
2016-12-27 06:50:03,495: Running on node SASServer6_2_prod.xxx.com
2016-12-27 06:50:03,495
2016-12-27 06:50:03,495: getting security manager
2016-12-27 06:50:03,495: Logging in for user-ID
2016-12-27 06:50:04,974: OK
Switched business context to XXX
2016-12-27 06:50:05,212
logon: SUCCESS
2016-12-27 06:50:05,212: Creating execution manager
2016-12-27 06:50:05,233: Executing...
ERROR 2016-12-27 06:50:05,583: EXCEPTION
ERROR com.sas.analytics.crm.ma.launcher.ExecutionFacade:doExecute
ERROR com.sas.analytics.crm.error.client.ApplicationException
at com.sas.analytics.crm.ma.launcher.wrapper.LauncherContext.logException(LauncherContext.java:93)
at com.sas.analytics.crm.ma.launcher.wrapper.LauncherContext.log(LauncherContext.java:85)
at com.sas.analytics.crm.ma.launcher.log.Log.throwing(Log.java:218)
at com.sas.analytics.crm.ma.launcher.log.Log.throwing(Log.java:200)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.doExecute(ExecutionFacade.java:654)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.execute(ExecutionFacade.java:195)
at com.sas.analytics.crm.ma.launcher.MALauncher.launch(MALauncher.java:613
at com.sas.analytics.crm.ma.launcher.MALauncher.wrappedMain(MALauncher.java:184)
at
com.sas.analytics.crm.ma.launcher.wrapper.WrappedLaunchCommand.run(WrappedLaunchCommand.java:42)
at
com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:17)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalStateException: No payload!
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.doExecute(ExecutionFacade.java:438)
. . .eight more error lines. . .
ERROR Additional information: No payload!
2016-12-27 06:50:03,495
2016-12-27 06:50:03,495: getting security manager
2016-12-27 06:50:03,495: Logging in for user-ID
2016-12-27 06:50:04,974: OK
Switched business context to XXX
2016-12-27 06:50:05,212
logon: SUCCESS
2016-12-27 06:50:05,212: Creating execution manager
2016-12-27 06:50:05,233: Executing...
ERROR 2016-12-27 06:50:05,583: EXCEPTION
ERROR com.sas.analytics.crm.ma.launcher.ExecutionFacade:doExecute
ERROR com.sas.analytics.crm.error.client.ApplicationException
at com.sas.analytics.crm.ma.launcher.wrapper.LauncherContext.logException(LauncherContext.java:93)
at com.sas.analytics.crm.ma.launcher.wrapper.LauncherContext.log(LauncherContext.java:85)
at com.sas.analytics.crm.ma.launcher.log.Log.throwing(Log.java:218)
at com.sas.analytics.crm.ma.launcher.log.Log.throwing(Log.java:200)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.doExecute(ExecutionFacade.java:654)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.execute(ExecutionFacade.java:195)
at com.sas.analytics.crm.ma.launcher.MALauncher.launch(MALauncher.java:613
at com.sas.analytics.crm.ma.launcher.MALauncher.wrappedMain(MALauncher.java:184)
at
com.sas.analytics.crm.ma.launcher.wrapper.WrappedLaunchCommand.run(WrappedLaunchCommand.java:42)
at
com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:17)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalStateException: No payload!
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.doExecute(ExecutionFacade.java:438)
. . .eight more error lines. . .
ERROR Additional information: No payload!
This problem occurs sporadically, and it happens only when the middle tier is clustered.
The only workaround is to stop one middle-tier cluster during the sasmalauncher execution.
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 Marketing Automation | Solaris for x64 | 6.3 | 9.4 TS1M1 | ||
| Linux for x64 | 6.3 | 9.4 TS1M1 | ||||
| HP-UX IPF | 6.3 | 9.4 TS1M1 | ||||
| 64-bit Enabled Solaris | 6.3 | 9.4 TS1M1 | ||||
| 64-bit Enabled AIX | 6.3 | 9.4 TS1M1 | ||||
| Microsoft® Windows® for x64 | 6.3 | 9.4 TS1M1 | ||||
A fix for this issue for SAS Marketing Automation 6.5 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/Z77.html#59634A fix for this issue for SAS Marketing Automation 6.4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/U53.html#59634A fix for this issue for SAS Marketing Automation 6.3 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/R60.html#59634| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2017-02-10 09:01:01 |
| Date Created: | 2017-01-05 10:37:36 |