ForgeRock Identity Platform
Does not apply to Identity Cloud

Troubleshooting AM and Agents

This book provides information on troubleshooting various issues in AM and Agents, including collecting useful troubleshooting information such as logs, heap dumps and stack traces.

Printer friendly view

Table of Contents

  • 1 Sending troubleshooting data to ForgeRock Support for analysis
  • 2 How do I record troubleshooting information in AM (All versions)?
  • 3 Best practice for recording troubleshooting information in AM (All versions)
  • 4 How do I check if AM (All versions) is up and running?
  • 5 How do I check what version of AM (All versions) I have installed?
  • 6 How do I export and import Service configurations for AM (All versions)?
  • 7 How do I export configuration details for the Agent (All versions)?
  • 8 How do I diagnose a hung AM (All versions) server?
  • 9 How do I troubleshoot Kerberos and WDSSO issues in AM (All versions)?
  • 10 How do I troubleshoot certificate-based authentication issues in AM (All versions)?
  • 11 How do I troubleshoot issues with the CORS filter in AM (All versions)?
  • 12 How do I troubleshoot WebSocket issues in Agents (All versions)?
  • 13 How do I collect data for troubleshooting high CPU utilization on AM (All versions) servers?
  • 14 How do I find which thread is consuming CPU in a Java process in AM (All versions)?
  • 15 Logging
    • 15.1 Where can I find useful logs for troubleshooting ForgeRock products?
    • 15.2 How do I trace transactions through the audit logs for troubleshooting across ForgeRock products?
    • 15.3 How do I enable Message level debugging in AM (All versions) debug files?
    • 15.4 How do I enable debug logging for troubleshooting Agents (All versions)?
    • 15.5 How do I enable message level debugging for install and upgrade issues with AM (All versions)?
    • 15.6 How do I enable message level debugging for ssoadm in AM (All versions)?
    • 15.7 How do I enable debug mode for troubleshooting Amster (All versions)?
    • 15.8 How do I enable debug logging for troubleshooting Kerberos and WDSSO issues in AM (All versions)?
    • 15.9 How do I enable message level debugging for the RADIUS server in AM (All versions)?
    • 15.10 How do I find network errors in the logs for the configuration store in AM (All versions)?
    • 15.11 How do I collect all the data required for troubleshooting AM and Agents (All versions)?
    • 15.12 How do I clear debug logs in AM (All versions)?
    • 15.13 How do I rotate AM 5.x and 6.x debug logs?
    • 15.14 How do I add logging to server-side scripts in AM (All versions)?
    • 15.15 How do I create a HAR file for troubleshooting AM (All versions)?
    • 15.16 How do I enable Garbage Collector (GC) Logging for AM (All versions)?
    • 15.17 How do I collect JVM data for troubleshooting AM (All versions)?
  • 16 How do I monitor session statistics in AM (All versions)?
  • 17 How do I clear stats logs in AM (All versions)?
  • 18 How do I stop stats logging in AM (All versions)?
  • 19 How do I avoid common issues with REST calls in AM (All versions)?
  • 20 How do I understand the underlying REST call being used in web requests in Identity Cloud or AM (All versions)?
  • 21 Performance Tuning
    • 21.1 FAQ: AM performance and tuning
    • 21.2 How do I change the JVM heap size for AM (All versions)?
    • 21.3 Best practice for JVM Tuning with G1 GC
    • 21.4 Best practice for JVM Tuning with CMS GC
    • 21.5 How do I improve the performance of ssoadm in AM (All versions)?