Advanced topics

Servlet: DBMonitor




This servlet does not return XML data and cannot be used by the Ant or Layout APIs.

The DBMonitor servlet tries to connect to the database using the current database settings.

It is used for server monitoring only.


Unless prevented by firewall or other network security, the DBMonitor URL should be publicly accessible on any PageSeeder server as:


While getting the standard response doesn't mean the system is free from problems, not getting it guarantees there are problems.

Successfully getting a response means that PageSeeder's key infrastructure (servlet container, web server, database) is live and communicating.


All responses are text only (text/plain). HTTP Status codes can be used to help diagnosing problems.

200 OK

If DBMonitor is able to connect and use the PageSeeder database, it will return the HTTP status code 200 (OK) and a simple text message.

It means that the DBMonitor was able to connect to the database using the current database properties and that it was able to make a simple query.


DBMonitor does not verify the integrity of the database. It can only assert that PageSeeder can access the database successfully. A successful response does not necessarily guarantee that the database is setup properly.

502 Bad Gateway

The HTTP status code 502 (Bad Gateway) is returned if there is any error related to the database. A message indicating the possible cause may be included in the response.

This error may occur because:

  • The database properties are incorrect;
  • The database service is not started;
  • The database server is unreachable (if on a different host);
  • The database server was not setup properly.

500 Internal Server Error

The HTTP status code 500 (Internal Server Error) is only returned if the DBMonitor itself is in an error state. This should rarely occur and it simply means that the DBMonitor is unable to provide any information about the system.

Server Timeout / Unreachable

When no status code is returned. It may be indicative of a more serious problem such as:

  • PageSeeder itself is not configured properly;
  • PageSeeder is too busy and has become unresponsive;
  • A network error (DNS, firewall, network security);
  • The entire system is down.

HTTP Method: GET

No parameters required for this request.

Created on , last edited on