If you submit a request to the SAS® Stored Process Server and the server
startup time is slow, the first request might fail with the following
error message:
Stored Process Error
Unable to execute stored process.
Unable to connect to a Stored Process server
For SAS® Stored Processes submitted from a Web–based client, an error similar to the
following might appear in one or more of the Web server log files:
[ERROR] (52e022f94e333f6c:65303277:11db191ca16:-5682, B0576920 MS)
com.sas.services.storedprocess.Execution - A connection could not be obtained.
com.sas.services.connection.FatalConnectionFactoryException: sam.S249.ex.msg:
A connection to server host 12.34.56.789 could not be established on port 8611.
Either there is no server listening for connections or the server is too busy
to accept any new connections. Make sure that the server has started and that
the values provided for host and port are correct.
However, if you submit the same request a second time, it might run successfully.
This problem is caused by the following scenario. The SAS Object Spawner
incorrectly informs load balancing that the SAS Stored Process Server is
ready to accept redirected clients before the server has actually
started listening for clients. Redirected clients can then get lost in
the redirect phase of the request:
Client (11.22.33.444:4408) connection accepted from listen port 8601
Redirecting client () to IP 12.34.56.789, port 8611
Server A5L9F66M.AW000002 has client (IP 11.22.33.444:4409) entering
In some cases, the SAS Stored Process
Server processes might become orphan processes.
If you encounter this problem, pre–start several SAS Stored Process
Servers as a workaround. For example, in your SAS® Management Console,
under Server Manager select:
SASMain ► Stored Process Server ► Properties ► Options
► Advanced Options ► Load Balancing Properties
Then, specify a value of 2 or more for Start Size.
If you specify a low Shutdown Inactivity Timeout value, the problem is
more likely to occur, because the SAS Stored Process Servers will be
shut down and started up more frequently. To avoid this problem, do not
specify a low Shutdown Inactivity Timeout value. The Shutdown
Inactivity Timeout value is specified on the same window as the Start
Size value.
The SAS Stored Process server could also be slow to start up if you
allocate numerous libraries in the autoexec file of your SAS Stored Process
Server (or have numerous pre–assigned libraries).
Operating System and Release Information
SAS System | SAS Integration Technologies | Microsoft Windows XP Professional | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Microsoft Windows 2000 Professional | 9.1 TS1M3 SP1 | |
Microsoft Windows 2000 Server | 9.1 TS1M3 SP1 | |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP1 | |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP1 | |
64-bit Enabled Solaris | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Linux on Itanium | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
z/OS | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Linux | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
HP-UX IPF | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
64-bit Enabled HP-UX | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
64-bit Enabled AIX | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
Tru64 UNIX | 9.1 TS1M3 SP1 | 9.2 TS2M0 |
*
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.