SUPPORT / SAMPLES & SAS NOTES
Problem Note 71150: A DS2 HTTP package becomes non-responsive and messages such as "Memory Error..." and "Freeing Memory Not Allocated..." appear in the logs
 |  |  |  |  |
When under a heavy load, the DS2 HTTP package might become non-responsive.
If DS2 is running in SAS® Federation Server, you might encounter errors in your logs such as the following:
20yy-mm-ddThh:mm:ss,sss ERROR [00035913] App.Program 32:userid - TKM: Memory Error [CHECKOWNER]
20yy-mm-ddThh:mm:ss,sss ERROR [00035913] App.Program 32:userid - Reason: [TKM Allocation Release Attempted to Wrong Pool]
20yy-mm-ddThh:mm:ss,sss ERROR [00035913] App.Program 32:userid - Pool Wrongly Selected [7fff3fb32e30 : d2http]
20yy-mm-ddThh:mm:ss,sss ERROR [00035913] App.Program 32:userid - Reason: [TKM Allocation Release Attempted to Wrong Pool]
20yy-mm-ddThh:mm:ss,sss ERROR [00035913] App.Program 32:userid - Pool Wrongly Selected [7fff3fb32e30 : d2http]
OR
ERROR: Freeing Memory Not Allocated Pool [0x7fffae53fc20] Value [0x7fffa5d83720] ******. Traceback for Thread [0x7ffff638f5d0] ******
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 | Base SAS | Linux for x64 | 9.4_M7 | 9.4 TS1M7 | ||