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

NPE in Enlinkd bridge topology broadcast domain calculation

    Details

      Description

      The following exception stack trace appears repeatedly in customer's output.log:

      Exception in thread "EnhancedLinkd-Thread-4-of-5" java.lang.NullPointerException
              at org.opennms.netmgt.model.topology.BroadcastDomain.calculateBFT(BroadcastDomain.java:422)
              at org.opennms.netmgt.model.topology.BroadcastDomain.calculateRootBFT(BroadcastDomain.java:387)
              at org.opennms.netmgt.enlinkd.NodeDiscoveryBridgeTopology.calculate(NodeDiscoveryBridgeTopology.java:823)
              at org.opennms.netmgt.enlinkd.NodeDiscoveryBridgeTopology.run(NodeDiscoveryBridgeTopology.java:712)
              at org.opennms.netmgt.enlinkd.scheduler.Scheduler$1.run(Scheduler.java:187)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
              at org.opennms.core.concurrent.LogPreservingThreadFactory$3.run(LogPreservingThreadFactory.java:124)
              at java.lang.Thread.run(Thread.java:745)
      

      It appears we're not defending against a null reference returned from a get on the HashMap containing the mapping of ifIndex to bridge port.

      The user also reports problems with heap exhaustion, though a causal relationship seems unlikely.

        Attachments

          Activity

            People

            • Assignee:
              rssntn67 Antonio Russo
              Reporter:
              jeffg Jeff Gehlbach
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: