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

enlinkd produces getReadyRunnable: queue is Empty

    XMLWordPrintable

Details

    Description

      I had run opennms one night without the Importer, so no rescans were triggered. This cause a bunch of these entries in the log. Are they really necessary on the warning state?
      2016-04-05 16:07:00,888 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
      2016-04-05 16:07:01,064 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
      2016-04-05 16:07:01,065 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
      2016-04-05 16:07:01,166 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
      2016-04-05 16:07:01,166 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty

      Attachments

        Activity

          People

            rssntn67 Antonio Russo
            rssntn67 Antonio Russo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: