Parameter:
DEBUG_XPAGES_REQUESTShort description: Logs the start time, runtime, and memory usage per XPages request – helpful for identifying slow XPages/Verse operations.
Profile
Parameter | DEBUG_XPAGES_REQUEST |
Category | Logging / Debug |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | 0 = off, 1 = basic, 2 = with stack trace on errors |
Description
When XPages or Verse applications respond unexpectedly slowly,
DEBUG_XPAGES_REQUEST=1 helps identify the most expensive requests. For each request, a line with the URL, wall time, JVM heap usage, and any errors is written to the HTTP/XPages log.Level 2 additionally provides stack traces on errors – valuable for developers but very chatty.
Example configuration
DEBUG_XPAGES_REQUEST=1
Notes & pitfalls
- Output lands in
xpages_log_*(/data/IBM_TECHNICAL_SUPPORT/).
- Complements
DEBUG_HTTPINOUT,XPAGES_TRACE_RENDER.
- For Verse, profiling runs in the same subsystem – also useful here.
- Enable level 2 only briefly on production servers.
- Takes effect immediately after
set config DEBUG_XPAGES_REQUEST=...– no restart required.