SAS Technical Support has received reports of previously working SAS Stored Process Servers becoming unresponsive over time for unknown reasons. By unresponsive, we mean that the SAS Stored Process Servers are up and running but no requests from client applications are getting through to the server. These servers might also be referred to as "hung" or "orphaned" SAS® processes.
What to do?
This document provides a suggested long–term strategy to facilitate this evaluation.
To examine this problem over time, we must modify the load balancing parameters for the SAS Stored Process Server to optimize server performance and add logging information to the Object Spawner and Stored Process Server logs. We’re not only looking for obvious errors in the logs but also clues as to a pattern to the problem, for example, what was the last step/program that successfully executed? What is the last entry written in the log?
Expand the Server Manager plug-in.
Balancing Algorithm: Cost
Response Refresh Rate: 0
Cost Per Client: 100
Logical Server Credentials: (None)
Maximum Clients: 5
Maximum Cost: 1000
Startup Cost: 10
Availability Timeout (msec): 60000
Start Size: 0
Recycle Activation Limit: 0
Inactivity Timeout: not selected, and blank
Windows Operating Systems:
<configdir>\Lev1\SASMain\ObjectSpawner\ObjectSpawner.bat
:install start /b "Object Spawner" "%sasdir%objspawn" –sasSpawnerCn "%SPWNNAME%" –OMRconfigfile "C:\SAS\EntBIServer\Lev1\SASMain\ObjectSpawner\OMRConfig.xml" –slf "C:\SAS\EntBIServer\Lev1\SASMain\ObjectSpawner\logs\objspawn.log" –sv –install –name "%SASServiceNAME%" %DEPENDS% goto end2
NOTE: The second line in the example above that begins with "start /b..." and the four lines which follow it must be specified on the SAME LINE in your ObjectSpawner.bat file. The long line above was split into multiple lines for readability. So, the line begins with "start /b" and ends with "%DEPENDS".
NOTE: The Object Spawner must be stopped and restarted to enable changes made to Object Spawner or Stored Process Server options in SAS Management Console or changes made in the Object Spawner or Stored Process Server script files.
UNIX Operating Systems:
!SASROOT/BIArch/Lev1/SASMain/ObjectSpawner/ObjectSpawner.sh
nohup $CMD –sasSpawnerCn "$SPWNNAME" –sv –slf $DIR/logs/objspawn.log –omrconfigfile $XMLCFG > $DIR/logs/objspawn_console.log 2>&1 &
NOTE: Object Spawner must be stopped and restarted to enable changes made to Object Spawner or Stored Process Server options in SMC or changes made in the Object Spawner or Stored Process Server script files.
Are you using custom style sheets in your stored process(es)?
See SAS Note 30783 "Using _ODSSTYLESHEET option or ODS HTML with STYLESHEET= can cause the Stored Process Server to become unresponsive or experience poor performance"
See SAS Note 30920 "_ODSSTYLESHEET option might be associated with a "Read Access Violation" error message or performance problems when running a stored process"
Are you using the Sessions feature of stored processes or are you producing graphics output in your stored process(es)?
See SAS Note 20387 "The SAS® Stored Process Server might temporarily stop executing requests when running a large number of sessions"
See SAS Note 19002 "The Stored Process Server may hang or experience slow performance when executing a stored process that creates graphics output"
Are you submitting your stored processes from a Web client?
See SAS Note 20670 "SAS® Stored Process Server "cost" might not be reclaimed if you close your Web browser while it is executing a stored process" *Hotfix included*
Are your Object Spawner and SAS Stored Process Servers running on a UNIX platform?
See SAS Note 17859 "Stored Process Server may "hang" on Unix if the DISPLAY environment variable is not set for the Object Spawner"
Are you using an older SAS image without service packs installed?
See SAS Note 14238 "Web Report Studio may cause the SAS Stored Process Server to hang" *WRS problem, fixed in sp2*
See SAS Note 14901 "Web Stored Process Server connections remain after closing client application " *SAS problem, fixed in sp2*
General debugging information for unresponsive SAS Stored Process Servers
See SAS Note 12516 ""Unable to connect to a Stored Process server" error message"
Once you believe there's a problem, save a copy of the objspawn.log file (grab it before you restart Object Spawner or it will be overwritten) and all of the SAS Stored Process Server logs that correspond to the same time frame when the problem occurred.
Here are some things you will need to think about:
If the problem can be isolated to a particular stored process or sequence of stored processes, use the macro code described in SAS Note 19573 "Macro that helps when debugging "hanging" Stored Process Server problems" to help identify the problematic step in the program.
If you are experiencing unresponsive stored process servers using SAS 9.2, please refer to the following notes:
Usage Note 43160: Tips for addressing unresponsive SAS® 9.2 Stored Process Servers, Part 1
Usage Note 43163: Tips for addressing unresponsive SAS® 9.2 Stored Process Servers, Part 2
Product Family | Product | System | SAS Release | |
Reported | Fixed* | |||
SAS System | SAS Integration Technologies | Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | |||
Microsoft Windows NT Workstation | 9.1 TS1M3 | |||
Microsoft Windows 2000 Professional | 9.1 TS1M3 | |||
Microsoft Windows 2000 Server | 9.1 TS1M3 | |||
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 | |||
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 | |||
Microsoft® Windows® for x64 | 9.1 TS1M3 | |||
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | |||
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 | |||
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 | |||
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 | |||
z/OS | 9.1 TS1M3 | |||
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | |||
Microsoft Windows XP Professional | 9.1 TS1M3 | |||
Windows Vista | 9.1 TS1M3 | |||
64-bit Enabled AIX | 9.1 TS1M3 | |||
64-bit Enabled HP-UX | 9.1 TS1M3 | |||
64-bit Enabled Solaris | 9.1 TS1M3 | |||
HP-UX IPF | 9.1 TS1M3 | |||
Linux | 9.1 TS1M3 | |||
OpenVMS Alpha | 9.1 TS1M3 | |||
Solaris for x64 | 9.1 TS1M3 | |||
Tru64 UNIX | 9.1 TS1M3 |
Type: | Usage Note |
Priority: |
Date Modified: | 2008-06-25 09:55:10 |
Date Created: | 2007-12-07 15:25:33 |