Adjust the Pinger Interval

Overview

You can configure how often the CMS web application sends a "pinger" callback to the server. The pinger keeps the authenticated session active and also retrieves changes made by other users. By default, the pinger runs every 20 seconds.

When to Adjust the Pinger Interval

Adjust the pinger interval if you need to:

Change how frequently the CMS checks in with the server to keep sessions alive.
Reduce server load by increasing the interval.
Ensure more frequent updates by decreasing the interval.

Prerequisites

Access to the JCR configuration, specifically /hippo:configuration/hippo:frontend/cms/cms-static/root.
Permissions to modify repository properties.

Configure the Pinger Interval

The pinger interval is controlled by the pinger.interval property under /hippo:configuration/hippo:frontend/cms/cms-static/root.

brXM 14

In brXM 14, specify the interval as a number followed by a time unit (for example, "seconds"). For supported formats, see the Duration.valueOf documentation.

To set the pinger to run every 90 seconds:

/hippo:configuration:
  /hippo:frontend:
    /cms:
      /cms-static:
        /root:
          pinger.interval: 90 seconds

brXM 15 and Later

Starting with brXM 15, use the ISO-8601 duration format PnDTnHnMn.nS for the interval value.

To set the pinger to run every 90 seconds:

/hippo:configuration:
  /hippo:frontend:
    /cms:
      /cms-static:
        /root:
          pinger.interval: PT90S

Disable the Pinger

To disable the pinger, set the interval to zero:

In brXM 14, use "0".
In brXM 15 and later, use "PT0S".

Example for brXM 15:

/hippo:configuration:
  /hippo:frontend:
    /cms:
      /cms-static:
        /root:
          pinger.interval: PT0S

Note: The pinger interval does not affect the automatic logout after user inactivity. The session will still expire after the configured timeout. For details, see Configure Active Logout.

Verification

After updating the configuration, verify that the new interval is effective by monitoring the network requests from the CMS web application or by observing session behavior.

Configure Active Logout