• Print |
• E-mail  |
• Bookmark

If a connection to the SAS/Integration Technologies 9.1 Object Spawner
fails due to an ERROR=122 (EIO), the Object Spawner will loop and
possibly consume excessive CPU.  The errors seen in the Object Spawner
log when this occurs are:

   ERROR: The TCP/IP accept call failed to process
   the operator connection. The returned error number is 122, and
   the text associated with that error is (An unexpected error has
   occurred.).
   ERROR: Bridge protocol engine socket access
   method was unable to accept a new client connection, error = 122
   (An unexpected error has occurred.).

The circumvention is to terminate the Object Spawner when an error=122
(EIO) occurs.  The Object Spawner will have to be restarted for future
connections to work.  When the Object Spawner terminates, existing
spawned IOM servers will not terminate.

The basic cause of an ERROR=122 (EIO) is the TCP/IP stack being
terminated and subsequently restarted.


A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#016954

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#016954

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :