SUPPORT / SAMPLES & SAS NOTES
Problem Note 62436: A SAS® LASR™ Analytic Server session terminates with "ERROR . . . Resource is write-locked by another thread"
 |  |  |  |  |
If you are running SAS LASR Analytic Server 2.8.1 in distributed mode, a memory leak might cause a LASR session to fail. Messages that are similar to the following are written to the log:
- OOM killer killed lasr session
- ERROR [00857519] 107155:sas - Resource is write-locked by another thread. File =/opt/sas/config/Lev1/SASMeta/MetadataServer/Logs/SASMeta_MetadataServer_2018-03-04_VWITVRSASV01_86422.log.
- ERROR [02846600] 1158401:sas - The file is already locked by another user.
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 LASR Analytic Server | Microsoft® Windows® for x64 | 2.81 | 2.81 | 9.4 TS1M5 | 9.4 TS1M5 |
| 64-bit Enabled AIX | 2.81 | 2.81 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| 64-bit Enabled Solaris | 2.81 | 2.81 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Linux for x64 | 2.81 | 2.81 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Solaris for x64 | 2.81 | 2.81 | 9.4 TS1M5 | 9.4 TS1M5 | ||