Problem Note 57792: SAS® Real-Time Decision Manager campaign fails with "org.apache.commons.dbcp.SQLNestedException: Borrow callableStatement from pool failed"
When you are running a SAS Real-Time Decision Manager campaign, you might notice a failure message from the SOAP envelope, such as the following:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/>
<SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring xml:lang="en">
org.apache.commons.dbcp.SQLNestedException: Borrow callableStatement from pool failed</faultstring>
</SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
The following error appears in the Federation Server directory\server1\var\log\dfs_*.log file.
Access Violation occurred during PREPARE at TKETSQLGenExpression+0x6c4:
2016-02-16T10:53:27,066 ERROR [00088635] App.Program 156:sasdmadm
-/opt/sas/sashome/SASFederationServer/4.1/fedserver/lib/tkepre.so(tktracex+0x2e)
[0x7fc30402b21e]
For example, when an outer query does not contain a table reference (such as in a FROM clause), but a subquery does (such as in a SELECT list), the problem occurs. The SAS Federated Query Language (FedSQL) incorrectly handles this situation by requiring that the column variable be initialized, which causes an invalid pointer.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Federation Server | Solaris for x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Linux for x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
HP-UX IPF | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
64-bit Enabled Solaris | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
64-bit Enabled AIX | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Ultimate x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Ultimate 32 bit | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Professional x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Professional 32 bit | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Home Premium x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Home Premium 32 bit | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Enterprise x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Windows 7 Enterprise 32 bit | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2012 Std | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Std | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Datacenter | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2012 Datacenter | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2008 for x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2008 R2 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows Server 2008 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 10 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 8.1 Pro x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 8.1 Pro 32-bit | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 8.1 Enterprise x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 8.1 Enterprise 32-bit | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 8 Pro x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 8 Pro 32-bit | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 8 Enterprise x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft Windows 8 Enterprise 32-bit | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
Microsoft® Windows® for x64 | 4.1_M1 | 4.1_M1 | 9.4 TS1M2 | 9.4 TS1M3 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2016-08-08 11:41:47 |
Date Created: | 2016-03-04 10:35:23 |