SNMP monitoring fails in AM 5.5.1 with No Monitoring interfaces started exception

Last updated Apr 12, 2021

The purpose of this article is to provide assistance if SNMP monitoring fails in AM with a "No Monitoring interfaces started; monitoring disabled" exception. You will also see "Ports are unable to be accessed resulting in".


This article has been archived and is no longer maintained by ForgeRock.


The following error is shown in the CoreSystem debug log when SNMP monitoring fails:

Ports are unable to be accessed resulting in: ERROR: Failed to start monitoring adapters - ignoring com.sun.identity.monitoring.MonitoringStartupException: No Monitoring interfaces started; monitoring disabled. at com.sun.identity.monitoring.MonitoringAdapters.<init>( at com.sun.identity.monitoring.MonitoringManager$MonitoringProvider.startMonitoringAdapters( at com.sun.identity.monitoring.MonitoringManager$NoopMonitoringProvider.startMonitoring( at com.sun.identity.monitoring.MonitoringManager.startMonitoring( at com.sun.identity.common.MonitoringConfigurator.init(

Recent Changes

Upgraded to, or installed AM 5.5.1.

Enabled SNMP monitoring.


The OpenDMK library (opendmk.jar) was removed, which prevents the SNMP ports from starting per known issue: OPENAM-12244 (Monitoring services unable to connect to Port).


This issue can be resolved by upgrading to AM 5.5.2 or later; you can download this from BackStage. Once you have upgraded, you must follow the steps in Setup and Maintenance Guide › To Enable the SNMP Monitoring Interface to install the OpenDMK library and enable monitoring.


You can workaround this issue by manually installing the OpenDMK library (opendmk.jar) that is shipped with DS 5.5.0, as follows:

  1. Download DS from BackStage.
  2. Extract the zip into a temporary directory, for example: temp/dj-5.5.0: $ cd temp/dj-5.5.0 $ unzip
  3. Run the OpenDMK library extractor (this launches a UI, so should be run on a local machine rather than via a SSH connection): $ cd temp/dj-5.5.0 $ java -jar snmp/opendmk.jar
  4. Review and accept the license.
  5. Install the the OpenDMK library into the temporary directory, for example: temp/opendmk.
  6. Copy the extracted jdmkrt.jar (located in the temp/opendmk/OpenDMK-bin/lib directory) to the relevant AM server(s):
    1. Stop the web application container in which AM runs. 
    2. Copy the jdmkrt.jar to /path/to/tomcat/webapps/openam/WEB-INF/lib directory where AM is deployed.
    3. Restart the web application container in which AM runs.

See Also

Performance tuning and monitoring ForgeRock products

Related Training


Related Issue Tracker IDs

OPENAM-12244 (Monitoring services unable to connect to Port)

Copyright and Trademarks Copyright © 2021 ForgeRock, all rights reserved.