javax.jmdns.impl.tasks.RecordReaper problem

[Henrik Lynggaard Hansen]

Hi

we am getting a lot (as in 11k+ over 2 days) of below error in our hudson logs.

Mar 24, 2011 10:29:59 PM javax.jmdns.impl.tasks.RecordReaper run
SEVERE: RecordReaper(scrbvirdefrm603.local.).Error while reaping
records: [Pointer@1522761125 type: TYPE_PTR index 12, class: CLASS_IN
index 1, name: _services._dns-sd._udp.local. ttl: '0/4500' alias:
'_workstation._tcp.local.']
java.lang.IllegalArgumentException: The instance name component of a
fully qualified service cannot be empty.
at javax.jmdns.impl.ServiceInfoImpl.checkQualifiedNameMap(ServiceInfoImpl.java:356)
at javax.jmdns.impl.ServiceInfoImpl.<init>(ServiceInfoImpl.java:197)
at javax.jmdns.impl.DNSRecord$Pointer.getServiceInfo(DNSRecord.java:540)
at javax.jmdns.impl.DNSRecord.getServiceInfo(DNSRecord.java:1051)
at javax.jmdns.impl.JmDNSImpl.renewServiceCollector(JmDNSImpl.java:1228)
at javax.jmdns.impl.tasks.RecordReaper.run(RecordReaper.java:80)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

It seems to be covered by
http://issues.hudson-ci.org/browse/HUDSON-8647
http://issues.jenkins-ci.org/browse/JENKINS-8647

but does the problem have any adverse effects on the stability or is
it "just" log spam ?

[Jason Dillon]

Why are you cross posting to hudson and jenkins?

Are you using DNS multicast? If not you may want to just disable it:

hudson.DNSMultiCast.disabled=true

--jason

[Mark Waite]

On Mar 24, 2011, at 3:49 PM, Henrik Lynggaard Hansen wrote:

> Hi
>
> we am getting a lot (as in 11k+ over 2 days) of below error in our hudson logs.
>
> Mar 24, 2011 10:29:59 PM javax.jmdns.impl.tasks.RecordReaper run
> SEVERE: RecordReaper(scrbvirdefrm603.local.).Error while reaping

> It seems to be covered by
> http://issues.hudson-ci.org/browse/HUDSON-8647
> http://issues.jenkins-ci.org/browse/JENKINS-8647
>
> but does the problem have any adverse effects on the stability or is
> it "just" log spam ?

I never saw any adverse effect on stability in the several weeks I was monitoring it.  

Several of our configurations have been running the 1.395 version (with the RecordReaper output) for many weeks, with no observed stability issues.  We see lots of output, but nothing else.

I've understood that the work around (disable DNS multicast) works.  I wasn't successful making it work, but others have reported it worked for them.

I think the best choice is to upgrade to a Jenkins version which fixes the bug.  If you can't do that, then the next best choice would be to disable DNS multicast.  If you can't do that, then the next best choice is to accept the log spam and manage it with your favorite log management tool.  I use logrotate on Debian and it handles the volume easily.

Mark Waite