Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-14973

Monitoring throws StackTrace even if JDMK isn't being used/needed.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.5.0, 6.5.1
    • Fix Version/s: 6.0.1, 6.5.2.1, 6.5.3, 7.0.0, 5.5.2
    • Component/s: None
    • Labels:
    • Sprint:
      AM Sustaining Sprint 64, AM Sustaining Sprint 65
    • Story Points:
      2
    • Needs backport:
      No
    • Support Ticket IDs:
    • Verified Version/s:
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Activate Monitoring like so:

      Configure > Global Services > Configuration (with monitoring.json (snmp disabled, http monitoring enabled)
      Configure > Global Services > Secondary Configurations > Add a prometheus config (can be simple).

      Whenever AM 6.5 starts, you'll get WARNING and ERROR messages in the logs:

      WARNING: Agent.startAgent:No Monitoring interfaces started; monitoring disabled.
      amMonitoring:05/08/2019 12:41:17:707 PM UTC: Thread[localhost-startStop-1,5,main]: TransactionId[c6e0095b-399c-4332-9969-7929984a12d0-0]
      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>(MonitoringAdapters.java:231)
             at com.sun.identity.monitoring.MonitoringManager$MonitoringProvider.startMonitoringAdapters(MonitoringManager.java:102)
             at com.sun.identity.monitoring.MonitoringManager$NoopMonitoringProvider.startMonitoring(MonitoringManager.java:144)
             at com.sun.identity.monitoring.MonitoringManager.startMonitoring(MonitoringManager.java:58)
             at com.sun.identity.common.MonitoringConfigurator.init(MonitoringConfigurator.java:63)
      

      This error message is displayed whenever neither SNMP / RMI monitoring is started, which shouldn't be the case if you just want Prometheus monitoring for instance. I suspect the monitoring check only checks to see if monitoring in general is turned on before checking if everything it needs is there at startup. However, this should be suppressed when it isn't needed if people are monitoring their log files.

        Attachments

          Activity

            People

            • Assignee:
              lawrence.yarham Lawrence Yarham
              Reporter:
              jeremy.cocks Jeremy Cocks
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: