Clients might encounter slow or failed requests when connecting to, or using, a Web application that is deployed on a tc Runtime instance.

About this task

A slow request is a request in which the exceeds a specified threshold. The default threshold is 500 seconds. A failed request is a request that did not execute.

Although the tc Runtime instance logs these errors in the log files, it can be difficult to pinpoint the origin of an error or to determine how to fix it.

The alert is not enabled by default.

When you enable thread diagnostics, tc Runtime provides additional information to assist you to troubleshoot the problem. The vRealize Hyperic alert is triggered when a request is slower than the specified threshold, or when it fails.

When you enable thread diagnostics, you can view the following contextual information about a slow or failed client request:

  • Time and date of the slow or failed request.

  • The URL invoked by the client that resulted in the slow or failed request.

  • The error returned by the request.

  • Any database queries that were executed as part of the request and how long each one took.

  • Whether any database connection failed or succeeded.

  • Whether the database had any other connectivity problems.

  • Whether the database connection pool ran out of connections.

  • Whether any garbage collection occurred during the request, and if so, how long it took.

Procedure

  1. Browse to the Views > Server Configurationconsole page for the ts Runtime instance.
  2. Click the Services tab.
  3. In the table, click the service to configure.

    The default tc Runtime service is Catalina.

  4. In the Thread Diagnostics section, select the Enable Thread Diagnostics property and click Save.
  5. Click the necessary links and buttons to push the configuration changes to the tc Runtime instance, and restart the instance.