Problem Note 36599: Connection failures to a SAS Pooled Workspace Server may occur under heavy load.
Connection failures to a SAS Pooled Workspace server may occur if a system runs out of ephemeral ports, or the range of ports used by the operating system for ephemeral ports includes the object spawner port bank.
The SAS Object Spawner log will contain the following error:
Failed to start server.
and/or ...
A port could not be obtained to allow the client to be connected to this server.
The SAS Pooled Workspace server log will contain the following error:
The TCP/IP tcpSockBind support routine failed with error 10048 (The specified address is already in use.).
On a Windows system prior to Windows Vista, the resolution is to raise the ephemeral port limit by setting the MaxUserPort value in the system registry to the max value of 65534.
How to increase the maximum number of ephemeral ports.
After setting the MaxUserPort value, the ports specified for the SAS Object Spawner port bank should be reserved so that the system does not try to use them as ephemeral ports. Default port numbers in the port bank are 8801, 8811, 8821.
How to reserve a range of ephemeral ports on a computer.
On a Linux system, edit the /etc/sysctl.conf file and add the following line:
# Allowed local port range
net.ipv4.ip_local_port_range = 32768 65000
The network and SAS® servers must be restarted for the change to take effect. The following command can be used to manually restart the network:
[root] /# /etc/rc.d/init.d/network restart
In a few instances, the Linux operating system had to be rebooted before the change took effect.
All other UNIX operating systems do not need these changes.
Operating System and Release Information
| SAS System | N/A | Windows Vista for x64 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 9.2 TS2M0 | 9.3 TS1M0 |
| Windows Vista | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 for x64 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft® Windows® for x64 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows XP 64-bit Edition | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M0 | 9.3 TS1M0 |
| z/OS | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M0 | 9.3 TS1M0 |
| 64-bit Enabled AIX | 9.2 TS2M0 | 9.3 TS1M0 |
| 64-bit Enabled HP-UX | 9.2 TS2M0 | 9.3 TS1M0 |
| 64-bit Enabled Solaris | 9.2 TS2M0 | 9.3 TS1M0 |
| HP-UX | 9.2 TS2M0 | 9.3 TS1M0 |
| HP-UX IPF | 9.2 TS2M0 | 9.3 TS1M0 |
| Linux | 9.2 TS2M0 | 9.3 TS1M0 |
| Linux for x64 | 9.2 TS2M0 | 9.3 TS1M0 |
| Linux on Itanium | 9.2 TS2M0 | 9.3 TS1M0 |
| OpenVMS on HP Integrity | 9.2 TS2M0 | 9.3 TS1M0 |
| Solaris for x64 | 9.2 TS2M0 | 9.3 TS1M0 |
| Tru64 UNIX | 9.2 TS2M0 | 9.3 TS1M0 |
*
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.
Connection attempts to a SAS Pooled Workspace Server may fail if a system runs out of ephemeral ports or the range of ports used by the operating system for ephemeral ports includes the SAS Object Spawner port bank.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2009-08-21 10:54:36 |
| Date Created: | 2009-07-23 11:06:38 |
