Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-12565

"No future found for message" warnings in telemetryd log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 25.2.0, 25.2.1
    • Fix Version/s: 26.0.0
    • Component/s: None
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Sprint:
      Horizon 2020 - Feb 19th

      Description

      telemetryd.log shows:

      2020-03-02 14:55:52,682 WARN  [OpenNMS.Sink.AsyncDispatcher.Telemetry-BMP-Thread-5] o.o.c.i.s.c.AsyncDispatcherImpl: No future found for message aaca95b9-8427-46dd-8377-873bb4771836=org.opennms.netmgt.telemetry.api.receiver.TelemetryMessage@301ca73
      2020-03-02 14:56:22,388 WARN  [RateLimitedLogRegistry-0] o.o.c.i.s.c.AsyncDispatcherImpl: (suppressed 265 logs similar to 'No future found for message {}' in PT29.705S)
      2020-03-02 14:56:22,507 WARN  [OpenNMS.Sink.AsyncDispatcher.Telemetry-BMP-Thread-6] o.o.c.i.s.c.AsyncDispatcherImpl: No future found for message 548e53d2-4e4e-4e59-be76-76f810de7543=org.opennms.netmgt.telemetry.api.receiver.TelemetryMessage@192b807f
      2020-03-02 14:56:22,515 WARN  [OpenNMS.Sink.AsyncDispatcher.Telemetry-BMP-Thread-3] o.o.c.i.s.c.AsyncDispatcherImpl: No future found for message 2ce06f9a-6515-47f6-a118-d635aaa9c24c=org.opennms.netmgt.telemetry.api.receiver.TelemetryMessage@5eb8fd9b
      2020-03-02 14:56:22,515 WARN  [OpenNMS.Sink.AsyncDispatcher.Telemetry-BMP-Thread-3] o.o.c.i.s.c.AsyncDispatcherImpl: No future found for message 3d5b47f5-37b3-419c-93e5-7d03b323498b=org.opennms.netmgt.telemetry.api.receiver.TelemetryMessage@7aa06e00
      2020-03-02 14:56:22,813 WARN  [OpenNMS.Sink.AsyncDispatcher.Telemetry-BMP-Thread-6] o.o.c.i.s.c.AsyncDispatcherImpl: No future found for message 9564da60-1d40-413b-9ace-0524cbedb04f=org.opennms.netmgt.telemetry.api.receiver.TelemetryMessage@6acd5191
      2020-03-02 14:56:22,911 WARN  [OpenNMS.Sink.AsyncDispatcher.Telemetry-BMP-Thread-2] o.o.c.i.s.c.AsyncDispatcherImpl: No future found for message b5bb472c-d80c-4f00-99b1-00b4e28ec553=org.opennms.netmgt.telemetry.api.receiver.TelemetryMessage@51675ea7
      

      I expect these to show up when off-heap is being used, but off-heap does not appear to be used in the case:

      # ls -alh /opt/opennms/data/
      total 44K
      drwxrwxr-x   7 root root 4.0K Feb 28 14:55 .
      drwxr-xr-x  14 root root 4.0K Feb 28 14:52 ..
      drwxrwxr-x 409 root root  12K Feb 28 14:53 cache
      drwxrwxr-x   2 root root 4.0K Feb 28 14:53 generated-bundles
      -rw-rw-r--   1 root root   42 Feb 28 14:55 history.txt
      drwxrwxr-x   2 root root 4.0K Feb 28 14:53 kar
      -rw-rw-r--   1 root root    5 Feb 28 14:53 port
      drwxrwxr-x   2 root root 4.0K Feb 28 14:53 security
      drwxrwxr-x   9 root root 4.0K Feb 28 14:53 tmp
      

      Are these messages expected during normal operation? Maybe we should change the level to INFO?

        Attachments

          Activity

            People

            Assignee:
            mbrooks Matthew Brooks
            Reporter:
            j-white Jesse White
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: