SAS Technical Support has received reports of previously working SAS Stored Process Servers becoming unresponsive over time for unknown reasons. Unresponsive means that the SAS Stored Process Servers are 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 do you do?
See SAS Note 43160 "Tips for addressing unresponsive SAS 9.2 Stored Process Servers, Part 1" for instructions on how to recover from the immediate problem of unresponsive servers.
This document provides a suggested long–term strategy to facilitate this evaluation.
To examine this problem over time, you must add logging information to the Object Spawner and stored process server logs. You are 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 or program that successfully executed? What is the last entry that was written in the log? The following SAS notes are useful:
Once you believe there is a problem, save a copy of the ObjectSpawner_yyyy-mm-dd_pid.log file and ObjectSpawner_console.log file (UNIX only) and all of the SAS Stored Process Server logs that correspond to the same time frame when the problem occurred. Be sure to collect the ObjectSpawner_console.log file before you restart the Object Spawner or it will be overwritten.
Here are some things that you need to consider:
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.1.3, refer to the following notes:
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: | 2011-06-21 15:20:55 |
Date Created: | 2011-05-05 10:56:12 |