Problem Note 61897: SAS® Federation Server becomes non-responsive in SAS® Real-Time Decision Manager and errors are generated
 |  |  |  |  |
When you use SAS Real-Time Decision Manager, the associated SAS Federation Server might appear to be non-responsive. In addition, attempts to stop the SAS Federation Server gracefully using the stop script might fail. You might also notice excessive time-outs while requests process in SAS® Decision Services.
This issue occurs most often, but is not restricted to, when you write contact history or perform dynamic treatment updates to the Common Data Model. Decision campaigns that return multiple treatments or that are associated with a number of dynamic treatment attributes tend to trigger this problem.
When this problem occurs, errors similar to the following might appear in your SAS Federation Server log:
Error 1
2018-02-13T17:56:04,093 ERROR [00013588] App.Program 116:sasfedadm@saspw - /local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepre.so(tktracex+0x2e) [0x7f2d6640cf5e]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepre.so(preExceptionHandler+0x89) [0x7f2d663d9c39]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bktExcept+0x62) [0x7f2d72de7f42]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bkt_signal_handler+0x144) [0x7f2d72de85a4]
/lib64/libpthread.so.0(+0xf7e0) [0x7f2d7412a7e0]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(skmPoolCachePut+0x4b) [0x7f2d72dfb95b]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepdl.so(+0x409d) [0x7f2d4a59c09d]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(sktMain+0x94) [0x7f2d72de5fd4]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bktMain+0x71) [0x7f2d72de7d81]
/lib64/libpthread.so.0(+0x7aa1) [0x7f2d74122aa1]
/lib64/libc.so.6(clone+0x6d) [0x7f2d737b0bcd]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepre.so(preExceptionHandler+0x89) [0x7f2d663d9c39]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bktExcept+0x62) [0x7f2d72de7f42]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bkt_signal_handler+0x144) [0x7f2d72de85a4]
/lib64/libpthread.so.0(+0xf7e0) [0x7f2d7412a7e0]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(skmPoolCachePut+0x4b) [0x7f2d72dfb95b]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepdl.so(+0x409d) [0x7f2d4a59c09d]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(sktMain+0x94) [0x7f2d72de5fd4]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bktMain+0x71) [0x7f2d72de7d81]
/lib64/libpthread.so.0(+0x7aa1) [0x7f2d74122aa1]
/lib64/libc.so.6(clone+0x6d) [0x7f2d737b0bcd]
Error 2
2018-02-13T17:56:04,134 ERROR [00013577] App.Program 119:sasfedadm@saspw - /local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepre.so(tktracex+0x2e) [0x7f2d6640cf5e]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepre.so(preExceptionHandler+0x89) [0x7f2d663d9c39]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bktExcept+0x62) [0x7f2d72de7f42]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bkt_signal_handler+0x144) [0x7f2d72de85a4]
/lib64/libpthread.so.0(+0xf7e0) [0x7f2d7412a7e0]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepre.so(preEnvFreeHandle+0x18) [0x7f2d663daee8]
/lib64/libc.so.6(clone+0x6d) [0x7f2d737b0bcd]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepre.so(preExceptionHandler+0x89) [0x7f2d663d9c39]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bktExcept+0x62) [0x7f2d72de7f42]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkmk.so(bkt_signal_handler+0x144) [0x7f2d72de85a4]
/lib64/libpthread.so.0(+0xf7e0) [0x7f2d7412a7e0]
/local/Mobile/QA/SASHome/SASFederationServer/4.2/fedserver/lib/tkepre.so(preEnvFreeHandle+0x18) [0x7f2d663daee8]
/lib64/libc.so.6(clone+0x6d) [0x7f2d737b0bcd]
Error 3
2018-02-16T11:56:12,341 ERROR [00008393] App.Statement.Statement.Execute2 118:sasfedadm@saspw - 58; sasfedadm; 1.1.5; T_EXECUTE2: Table Service: Function failed. Diagnostics: SQLState=42000, NativeRC=80FFF86B, Text: Syntax error or access violation. Diagnostics: SQLState=HY000, NativeRC=3C0FCF5F, Text: Unrecoverable error during execution of DS2 method. Prepared statement is no longer valid.. Diagnostics: SQLState=HY000, NativeRC=867FD00C, Text: EXECUTE failed for ...
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 Real-Time Decision Manager | Microsoft® Windows® for x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 |
| Microsoft Windows 8 Enterprise 32-bit | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows 8 Enterprise x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows 8 Pro 32-bit | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows 8 Pro x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows 8.1 Enterprise x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows 8.1 Pro 32-bit | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows 8.1 Pro x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows 10 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows Server 2008 | 6.5 | 9.4 TS1M3 | ||||
| Microsoft Windows Server 2008 R2 | 6.5 | 9.4 TS1M3 | ||||
| Microsoft Windows Server 2008 for x64 | 6.5 | 9.4 TS1M3 | ||||
| Microsoft Windows Server 2012 Datacenter | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows Server 2012 R2 Std | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Microsoft Windows Server 2012 Std | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Windows 7 Enterprise 32 bit | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Windows 7 Enterprise x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Windows 7 Home Premium 32 bit | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Windows 7 Home Premium x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Windows 7 Professional 32 bit | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Windows 7 Professional x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Windows 7 Ultimate 32 bit | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Windows 7 Ultimate x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| 64-bit Enabled AIX | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| 64-bit Enabled Solaris | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| HP-UX IPF | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Linux for x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
| Solaris for x64 | 6.5 | 6.6 | 9.4 TS1M3 | 9.4 TS1M6 | ||
A fix for this issue for SAS Federation Server 4.2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/Y46.html#61897| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2018-03-28 10:10:07 |
| Date Created: | 2018-02-27 13:51:10 |