When running a request using the SAS/IntrNet Application Dispatcher, if
the Web server exceeds its "cgi timeout" value before the request
completes execution, the Web server may "kill" the IntrNet Broker.  This
will cause the connection to be broken between the IntrNet Broker and
the IntrNet Application Dispatcher and may result in the following error
messages in your IntrNet Application Server log file:

   ERROR: Application Server lost connection to Application Broker.
   This can happen if the Broker has timed out waiting for a response.
   ERROR: send call failed, system error is '10054 - WSAECONNRESET'.
   FATAL: Unrecoverable I/O error detected in the execution of the
   data step program.  Aborted during the EXECUTION phase.

If you suspect that your Web server is "killing" the IntrNet Broker, you
can run the test below (which removes the Web server from the scenario):

   1.  On your Web Server machine, bring up a shell prompt
       (on Windows, bring up a DOS prompt; on UNIX bring up
       a UNIX shell prompt).

   2.  Use the "cd" command to move to the directory where your
       Broker resides ("broker.exe" on Windows or "broker" on
       UNIX).

   3.  Issue the command below from the shell prompt
       (where "sample.test2.sas" is your long-running SAS
       job and "default" is your Service name):

         > broker "_service=default&_program=sample.test2.sas"

   4.  If this test runs successfully (while the same
       request fails with the above-mentioned error message),
       then it is very likely that your Web server is "killing"
       your IntrNet Broker.

Some Web Servers (such as Microsofts IIS 6.0) may "kill" the Broker if a
user clicks the Web Browser's "STOP" button after submitting a request
(and before the request has completed).  In this case, the same error
messages may appear in your IntrNet Application Server's SAS log file.

Operating System and Release Information