SAS client connections to the Object Spawner and SAS Metadata Server are not closed properly when the following are true:

• The SAS client application is a Java application (such as SAS^® Studio).
• The workspace server is configured to use SAS Token authentication.
• The client is redirected from one spawner to a different spawner to have the workspace server started.

When the client connects into the initial spawner, a new connection is established with the SAS Metadata Server to authenticate the user. If the client is then redirected to a different spawner, the connection that was opened to the SAS Metadata Server to authenticate the user and the initial connection to the Object Spawner by the client application are not closed. These connections remain open until the user restarts the spawner. The buildup of open connections might lead to resource depletion (such as file handles and ephemeral ports). 

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Grid Manager Plug-ins for SAS Management Console 9.4_M7 is available at:

A fix for this issue for SAS Deployment Backup and Recovery Tool 9.45 is available at:

A fix for this issue for SAS Management Console 9.4_M7 is available at:

A fix for this issue for SAS Job Flow 9.47 is available at: