Request timed out - Gateway Caching Server - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Gateway Caching Server

Platform
OnBase
Product
Gateway Caching Server
Release
Foundation 23.1
License
Standard
Essential
Premier

After users attempt to view or upload very large documents, the attempt fails and the following message is logged to the Diagnostics Console:

  • Request timed out

This message is displayed when the requested action (such as uploading or downloading a document) takes longer than the configured execution timeout.

The execution timeout specifies the number of seconds the application has to execute a request before the request times out. Depending on your network architecture, you may need to increase the execution timeout at one of the following levels:

  • Application Server

  • Web Server

  • Gateway Caching Server

If users' requests are passing through more than one of these applications, start with the application that has the lowest execution timeout. To increase the execution timeout:

  1. Open the application's Web.config file.
  2. Locate the executionTimeout setting.
    Note:

    The Gateway Caching Server's Web.config file does not contain an executionTimeout setting. As a result, it uses the default ASP.NET execution timeout of 110 seconds. Add <httpRuntime executionTimeout="110"/> on a new line directly above the </configuration> tag in the Gateway Caching Server's Web.config file, and modify the value accordingly.

  3. Specify (in seconds) how long the server should allow a request to be executed.

    Keep in mind this value controls how long the server is allowed process a user's request. If the server cannot execute the user's request within the period allowed, the user will have to wait the entire duration of the executionTimeout before an error is logged.

    Note:

    If you intend to export PCL documents to PDF, the executionTimeout value must be set to 86000. This allows an export to succeed without timing out.

  4. Save the Web.config file.
  5. Test whether the issue is resolved. If it is not, then repeat these steps as needed until the executionTimeout is large enough for the request to be executed. You may need to perform these steps for more than one server application.
    Tip:

    For assistance troubleshooting timeout issues, contact your first line of support.