Connections to a grid-launched stored process server might fail in a multi-object spawner environment. Typically, the error that is returned is Connection Refused. This error also includes the following information:

• the host name of the machine on which the stored process server is started
• the MultiBridge port on which the stored process server is instructed to listen for the incoming client

Note: By default, the MultiBridge ports are 8611, 8621, and 8631.

In addition, the following errors are written to the stored-process server log:

The TCP/IP tcpSockBind support routine failed with error 10048 (The specified address is already in use.).
Bridge Protocol Engine Socket Access Method was unable to bind the listen socket to port 8611.
The Bridge Protocol Engine Socket Access Method listen thread failed during the definition of the server listen.

This problem occurs when the stored process server is started on a machine that is remote to the launching object spawner.

There are two workarounds.

First Workaround

Define and start the object spawner on one machine only. This workaround is allowed in grid-launch cases because the grid daemons on the remote nodes actually perform the launch rather than the object spawners.

Second Workaround

1. Log on to SAS^® Management Console.
2. On the Plug-ins tab, select Server Manager ► application-server-context (for example, SASApp).
3. Right-click Logical Stored Process Server and select Properties.
4. In the Logical Stored Process Server Properties dialog box, click the Load Balancing tab and make sure that the Launch servers via Grid check box is not selected.



5. Close the Logical Stored Process Server Properties dialog box.
6. If you cleared the check box, restart the object spawners to enforce the change.

Operating System and Release Information