Problem Note 38070: The SAS Object Spawner might stop functioning properly if the -hostknownby option is used
 |  |  |  |  |
If the -hostknownby option is specified when you start the SAS Object Spawner, then an extra connection might be opened and not released each time that a new SAS Pooled Workspace Server is started. Over time, this extra connection can cause all sockets to become exhausted so that additional connections cannot be opened. When this situation occurs, all servers that are started by the SAS Object Spawner such as the SAS Pooled Workspace Server, SAS® Stored Process Server, or SAS Workspace Server stop functioning.
If you encounter this problem, then the following messages might write to your Object Spawner log file:
ERROR [#465856] The TCP/IP tcpSockAccept support routine failed with error 24 (Too many files are open.).
WARN [#465857] The Bridge Protocol Engine Socket Access Method listen thread was unable to accept a connection attempt from listen port xxxx due to too many active open handles. The listen associated with port xxxx will be removed for a brief period of time.
When you encounter this problem, you must stop and restart the SAS Object Spawner to release the connections. However, over time as new SAS Pooled Workspace Servers are started and stopped many times, the sockets become slowly exhausted again.
You might be able to work around this problem by setting the Inactive process shutdown timeout to 0 for the SAS Pooled Workspace Server. Then, the SAS Pooled Workspace Servers will be started and not shut down so that only a few extra sockets are used.
This option can be changed in the Plug-ins tab in SAS® Management Console 9.2:
- Select Server Manager ► SASApp ► SASApp - Logical Pooled Workspace Server.
- Right-click SASApp - Logical Pooled Workspace Server and select Properties.
- Click the Options tab.
- Click the Advanced Options button.
- Click the Load Balancing tab.
- Change the Inactive process shutdown timeout (sec): option to 0.
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 | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS Integration Technologies | z/OS | 9.2 TS2M0 | 9.2 TS2M3 |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows XP 64-bit Edition | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft® Windows® for x64 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows XP Professional | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Windows Vista | 9.2 TS2M0 | 9.2 TS2M3 | ||
| 64-bit Enabled AIX | 9.2 TS2M0 | 9.2 TS2M3 | ||
| 64-bit Enabled HP-UX | 9.2 TS2M0 | 9.2 TS2M3 | ||
| 64-bit Enabled Solaris | 9.2 TS2M0 | 9.2 TS2M3 | ||
| HP-UX IPF | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Linux | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Linux for x64 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| OpenVMS on HP Integrity | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Solaris for x64 | 9.2 TS2M0 | 9.2 TS2M3 | ||