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

Lots of "Unable to obtain lock for PollableNode before timeout" on Pollerd

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 14.0.0
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Latest compilation of 14.0.0 with a simple configuration

      Description

      On my machine running latest snapshot of 14.0.0 with Oracle Java 7u67, I'm seeing lots of messages like the following on poller.log:

      2014-10-16 16:26:21,908 ERROR [Poller-Thread-23-of-30] o.o.n.p.p.PollableElement: Unexpected exception: Unable to obtain lock for PollableNode [10] before timeout
      org.opennms.netmgt.poller.pollables.LockUnavailable: Unable to obtain lock for PollableNode [10] before timeout
          at org.opennms.netmgt.poller.pollables.PollableNode$Lock.obtain(PollableNode.java:82) ~[opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.poller.pollables.PollableNode.obtainTreeLock(PollableNode.java:309) ~[opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.poller.pollables.PollableElement.obtainTreeLock(PollableElement.java:212) ~[opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.poller.pollables.PollableElement.withTreeLock(PollableElement.java:263) [opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.poller.pollables.PollableElement.withTreeLock(PollableElement.java:250) [opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.poller.pollables.PollableService.doRun(PollableService.java:405) [opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.poller.pollables.PollableService.run(PollableService.java:386) [opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.scheduler.Schedule.run(Schedule.java:142) [opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.scheduler.Schedule$ScheduleEntry.run(Schedule.java:86) [opennms-services-14.0.0-SNAPSHOT.jar:?]
          at org.opennms.netmgt.scheduler.LegacyScheduler$1.run(LegacyScheduler.java:209) [opennms-services-14.0.0-SNAPSHOT.jar:?]
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_67]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_67]
          at org.opennms.core.concurrent.LogPreservingThreadFactory$3.run(LogPreservingThreadFactory.java:124) [opennms-util-14.0.0-SNAPSHOT.jar:?]
          at java.lang.Thread.run(Thread.java:745) [?:1.7.0_67]
      

      On a customer installation running an older snapshot of 14.0.0, the problem exist as well.

      I'm not sure if this is actually a problem, or something benign that we can ignore, but I think it is important to verify if Pollerd is not being affected by this problem.

        Attachments

          Activity

            People

            • Assignee:
              brozow Matt Brozowski
              Reporter:
              agalue Alejandro Galue
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: