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

OpenNMS start-up error - javax.jmdns.impl.tasks.state.DNSStateTask

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.10.5
    • Fix Version/s: 1.10.9, 1.11.90
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Debian Squeeze x86_64, java version "1.6.0_26"

      Description

      I sometimes see errors like this on start-up.

      17-Sep-2012 10:59:13 javax.jmdns.impl.tasks.state.DNSStateTask run
      WARNING: Prober(pehdon01.local.).run() exception
      java.io.IOException: Operation not permitted
      at java.net.PlainDatagramSocketImpl.send(Native Method)
      at java.net.DatagramSocket.send(DatagramSocket.java:625)
      at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537)
      at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131)
      at java.util.TimerThread.mainLoop(Timer.java:512)
      at java.util.TimerThread.run(Timer.java:462)
      17-Sep-2012 10:59:13 javax.jmdns.impl.tasks.state.DNSStateTask run
      WARNING: Prober(pehdon01.local.).run() exception
      java.io.IOException: Operation not permitted
      at java.net.PlainDatagramSocketImpl.send(Native Method)
      at java.net.DatagramSocket.send(DatagramSocket.java:625)
      at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537)
      at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131)
      at java.util.TimerThread.mainLoop(Timer.java:512)
      at java.util.TimerThread.run(Timer.java:462)
      17-Sep-2012 10:59:13 javax.jmdns.impl.JmDNSImpl __recover
      WARNING: RECOVERING
      17-Sep-2012 10:59:13 javax.jmdns.impl.JmDNSImpl __recover
      WARNING: RECOVERING
      17-Sep-2012 10:59:15 javax.jmdns.impl.JmDNSImpl __recover
      WARNING: pehdon01.local.recover() We are back!
      17-Sep-2012 10:59:15 javax.jmdns.impl.JmDNSImpl __recover
      WARNING: pehdon01.local.recover() We are back!

      It's strange, as the error doesn't always appear, only sometimes.
      I'm wondering what it really means, if it's causing a problem, and if it's a bug or not - so I thought the best thing to do was just log a bug and see what the conclusion is.

      Cheers,
      Just

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ranger Benjamin Reed
                Reporter:
                nysasounds@googlemail.com jcat
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: