If you publish a large package to the SAS^® Content Server and run the job several times, the job will cause SAS to become unresponsive. The amount of time that the job runs before SAS becomes unresponsive is random but it is usually more than 8 times.

The problem occurs because the HTTP client library is not registering a wait event for each attempt to read from the socket. The HTTP client library has to wait for available data on the socket when it is called directly from MVA so that it does not cause MVA to halt.

In the case of a failure, the client library has to make multiple reads to get enough data from the server in order to process the server response. The server's response is broken up into several packets and is encrypted. The client library sets up an event to wait for the available data, but it only does this once. It should be done for each attempt.

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 Base SAS 9.21_M1 is available at:

A fix for this issue for Base SAS 9.21_M3 is available at: