Documentation forDatabase Performance Analyzer

Advanced configuration for the DPA Central Server

You may need to change the Central Server configuration to make it run more efficiently in your environment.

To change the default behavior:

  1. Open the file in a text editor. This file is located in the following directory on your Central Server:


  2. Add one or more of the settings described below, and save the file.

General Central Server settings

Setting Value Description

true (default)


Enables or disables the use of Central Server mode. .token.login.supported

true (default)


Enables or disables the use of encrypted login tokens when jumping from the Central Server to a remote instance.

If true, a web service call authenticates the user and creates a temporary token to identify the incoming user and bypass the login process.

If false, the user is always prompted to log in to the remote instance.


false (default)

Determines which users see failures in the Unavailable DPA Servers section.

If true, all users see failures for all instances.

If false, only administrators see failures. Set this option to false if you do not want all users to know about other DPA instances in the organization.

true (default)


Enables or disables a process that performs simple checks on the file when DPA starts.

For example, flagging any local instances as the Central Server. Warning

The minimum message level to include on the Alarm Details tab. Valid values are below. If (empty) is set, details are disabled.

  • Critical
  • Warning
  • Normal
  • (empty) 200 The number of detail rows to show on the Alarm Details tab.

Thread pool settings

These settings control the number of threads that are used by the Central Server to make web service calls to other remote servers. The default settings are set for a few concurrent users hitting up to 100 remote instances. If you have more than 100 instances or many concurrent users, SolarWinds recommends adjusting these settings higher.

Setting Value Description 50 The core number of threads that Central Server uses to make web service calls to remote servers. 150 The maximum number of threads that Central Server uses to make web service calls to the remote servers. Central Server adds more threads only when all core threads are in use and the task queue is full. 5000 The maximum number of requests in the queue before Central Server either creates new threads to help with the work or rejects the request. Tasks are rejected if all 40 threads cannot keep up with the requests being made. 120 The number of seconds to keep an idle thread before removing it.

Client factory cache

A client factory creates web service clients that talk to remote instances on a per-user basis. One client factory is created per host:port combination (not per user), so the same factory is used to create individual clients for different users. Factory creation is resource-intensive because an initial handshake is done between the client and server, and kept in a cache for reuse.

Setting Value Description 100

The maximum number of client factories held in the cache.

The default is 100, which equates to 100 unique remote DPA instances.

Increase this value if you are connecting to more than 100 remote instances. 1800

The number of seconds a client factory remains in the cache without being used.

The default is 1800 seconds, which is equal to 30 minutes. 15

The number of seconds a client attempts to establish a connection before it times out.

The default is 15.

Zero (0) specifies that the client will continue to attempt to open a connection indefinitely. 30

The number of seconds the client waits for a response before it times out.

The default is 30 seconds.

Zero (0) specifies that the client will wait indefinitely.


false (default)

Enables or disables HTTP chunking.

False is the safer option.

true (default)


Enables logging of inbound and outbound messaging to capture the web service calls. Log levels are still controlled in the log4j.xml file.

Set this value to false to disable logging.