Skip to content

[JENKINS-8647] Hudson 1.395 logs many messages about RecordReaper IllegalArgumentException  #15585

Closed
Bug
Closed
[JENKINS-8647] Hudson 1.395 logs many messages about RecordReaper IllegalArgumentException #15585
Bug
Labels
component:coreimported-jira-issuepriority:majorresolution:fixed

Description

@jenkins-infra-bot
jenkins-infra-bot
opened on Jan 28, 2011

I'm seeing new diagnostic output on several different machines running Hudson
since I updated to 1.395.

Machines which have shown these types of messages from the master server
include:

  • Windows Server 2008 x64
  • Debian i386
  • Debian AMD64

The message is:

Jan 24, 2011 4:59:53 PM javax.jmdns.impl.tasks.RecordReaper run
SEVERE: RecordReaper(mwaite2-deb.local.).Error while reaping records:
[Pointer@​21075506 type: TYPE_PTR index 12, class: CLASS_IN index 1, name:
_services._dns-sd._udp.local. ttl: '2240/4500' alias:
'_home-sharing._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.(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)
Jan 24, 2011 4:59:54 PM javax.jmdns.impl.tasks.RecordReaper run
SEVERE:---- Local Host -----
local host info[mwaite2-deb.local., eth0:132.253.117.116, DNS:
mwaite2-deb.local. state: announced task: Renewer(mwaite2-deb.local.) state:
announced]
---- Services -----
Service: hudson (14)._hudson._tcp.local.:
[ServiceInfoImpl@​11418595 name: 'hudson (14)._hudson._tcp.local.' address:
'mwaite2-deb.ptcnet.ptc.com/132.253.117.116:80' status: 'DNS: mwaite2-deb.local.
state: announced task: Renewer(mwaite2-deb.local.) state: announced', has data
\020slave-port=35469+url=http://mwaite2-deb.ptcnet.ptc.com:8080/\015version=1.395]

---- Types ----
Type: _afpovertcp._tcp.local.: no subtypes
Type: _hudson._tcp.local.: no subtypes

Originally reported by -1, imported from: Hudson 1.395 logs many messages about RecordReaper IllegalArgumentException
  • status: Closed
  • priority: Major
  • component(s): core
  • resolution: Fixed
  • resolved: 2011-02-24T08:47:02+00:00
  • votes: 4
  • watchers: 13
  • imported: 2025-11-24
Raw content of original issue 
I'm seeing new diagnostic output on several different machines running Hudson 
since I updated to 1.395.



Machines which have shown these types of messages from the master server 
include:



    
	
  • Windows Server 2008 x64
    • 
	
  • Debian i386
    • 
	
  • Debian AMD64
    • 





The message is:



Jan 24, 2011 4:59:53 PM javax.jmdns.impl.tasks.RecordReaper run
SEVERE: RecordReaper(mwaite2-deb.local.).Error while reaping records: 
[Pointer@21075506 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: 
_services._dns-sd._udp.local. ttl: '2240/4500' alias: 
'_home-sharing._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)
Jan 24, 2011 4:59:54 PM javax.jmdns.impl.tasks.RecordReaper run
SEVERE:        ---- Local Host -----
        local host info[mwaite2-deb.local., eth0:132.253.117.116, DNS: 
mwaite2-deb.local. state: announced task: Renewer(mwaite2-deb.local.) state: 
announced]
        ---- Services -----
                Service: hudson (14)._hudson._tcp.local.: 
[ServiceInfoImpl@11418595 name: 'hudson (14)._hudson._tcp.local.' address: 
'mwaite2-deb.ptcnet.ptc.com/132.253.117.116:80' status: 'DNS: mwaite2-deb.local. 
state: announced task: Renewer(mwaite2-deb.local.) state: announced', has data
\020slave-port=35469+url=http://mwaite2-deb.ptcnet.ptc.com:8080/\015version=1.395]



        ---- Types ----
                Type: _afpovertcp._tcp.local.: no subtypes
                Type: _hudson._tcp.local.: no subtypes
  • environment: Debian, Windows
1 attachment

Activity

  1. jenkins-infra-bot commented on Jan 28, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jan 28, 2011
    Author
    MarkEWaite:

    The resulting log files tend to be large. Refer to information on the Hudson users mailing list http://groups.google.com/group/hudson-users/browse_thread/thread/323af7e50a7bb9bc/3ca3c46bd780524b

  2. jenkins-infra-bot commented on Feb 10, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 10, 2011
    Author
    rickard_von_essen:

    holgerhoffstaette have a solution see http://issues.hudson-ci.org/browse/HUDSON-8647

    holgerhoffstaette added a comment - 01/Feb/11 09:52 AM
    Easily fixed by dropping in the latest jmdns-3.4.0 jar (from http://sourceforge.net/projects/jmdns/). No more excess logging.

    I have updated the core/pom.xml to use jmdns-3.4.0.jar

    A fix is available at:
    rickard-von-essen@c59a00f
    and I've attached a patch.

  3. jenkins-infra-bot commented on Feb 10, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 10, 2011
    Author
    rickard_von_essen:
    • Original comment link
    • Raw content of original comment: 
      Git Patch to change the core/pom.xml to use jmdns-3.4.0

    Git Patch to change the core/pom.xml to use jmdns-3.4.0

  4. jenkins-infra-bot commented on Feb 14, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 14, 2011
    Author
    jieryn:
    • Original comment link
    • Raw content of original comment: 
      Did you test this? I don't think you even did the most basic kind of checking.. the program will not compile with this simple fix applied.

    Did you test this? I don't think you even did the most basic kind of checking.. the program will not compile with this simple fix applied.

  5. jenkins-infra-bot commented on Feb 14, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 14, 2011
    Author
    jieryn:

    I believe I have fixed this properly with #54

  6. jenkins-infra-bot commented on Feb 14, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 14, 2011
    Author
    scm_issue_link:
    • Original comment link
    • Raw content of original comment: 
      Code changed in jenkins
User: Jesse Farinacci
Path:
 core/pom.xml
 core/src/main/java/hudson/DNSMultiCast.java
http://jenkins-ci.org/commit/core/53f0274753d7a90a47726831011fa35874c83056
Log:
[FIXED JENKINS-8647] Many messages about RecordReaper IllegalArgumentException
      


      I did a checkout for our internal fork of JmDNS [1] and the
upstream version [2] to compare what the differences were..
I found none. There do not appear to be any local edits to
our fork so I can not figure out why we did the fork to
begin with.
      


      Perhaps some older version had locally patched bugs which
have since been resolved? Anyhow, given that JENKINS-8647
is causing lots of people lots of grief, and it is enabled
by default, I went ahead and bumped to jmdns-3.4.0 upstream.
      


      I think reduction of forks for library projects is generally
good, and especially when we have no practical changes made
to our version.
      


      [1] https://github.com/jenkinsci/jmdns
[2] https://jmdns.svn.sourceforge.net/svnroot/jmdns/tags/JmDNS_3_2_1/

    Code changed in jenkins
    User: Jesse Farinacci
    Path:
    core/pom.xml
    core/src/main/java/hudson/DNSMultiCast.java
    http://jenkins-ci.org/commit/core/53f0274753d7a90a47726831011fa35874c83056
    Log:
    [FIXED JENKINS-8647] Many messages about RecordReaper IllegalArgumentException

    I did a checkout for our internal fork of JmDNS [1] and the
    upstream version [2] to compare what the differences were..
    I found none. There do not appear to be any local edits to
    our fork so I can not figure out why we did the fork to
    begin with.

    Perhaps some older version had locally patched bugs which
    have since been resolved? Anyhow, given that JENKINS-8647
    is causing lots of people lots of grief, and it is enabled
    by default, I went ahead and bumped to jmdns-3.4.0 upstream.

    I think reduction of forks for library projects is generally
    good, and especially when we have no practical changes made
    to our version.

    [1] https://github.com/jenkinsci/jmdns
    [2] https://jmdns.svn.sourceforge.net/svnroot/jmdns/tags/JmDNS_3_2_1/

  7. jenkins-infra-bot commented on Feb 14, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 14, 2011
    Author
    scm_issue_link:

    Code changed in jenkins
    User: Jesse Farinacci
    Path:
    changelog.html
    http://jenkins-ci.org/commit/core/22d2dc487ddb5558694efd3d17e49d07adda19b3
    Log:
    update changelog for fix to JENKINS-8647

  8. jenkins-infra-bot commented on Feb 14, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 14, 2011
    Author
    rickard_von_essen:
    • Original comment link
    • Raw content of original comment: 
      jieryn
      


      I did rebuild the war. I thought this was why we have CI. Actually the fix runs, but as you point out, don't compile. But it's not rocket surgery to fix the problem, I see you already did.

    jieryn

    I did rebuild the war. I thought this was why we have CI. Actually the fix runs, but as you point out, don't compile. But it's not rocket surgery to fix the problem, I see you already did.

  9. jenkins-infra-bot commented on Feb 14, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 14, 2011
    Author
    dogfood:
    • Original comment link
    • Raw content of original comment: 
      Integrated in  jenkins_main_trunk #512
     [FIXED JENKINS-8647] Many messages about RecordReaper IllegalArgumentException
update changelog for fix to JENKINS-8647
      


      Kohsuke Kawaguchi : 
Files : 
      

        
	
      • core/src/main/java/hudson/DNSMultiCast.java
        • 
	
      • core/pom.xml
        • 

      



      Kohsuke Kawaguchi : 
Files : 
      

        
	
      • changelog.html
        •

    Integrated in jenkins_main_trunk #512
    [FIXED JENKINS-8647] Many messages about RecordReaper IllegalArgumentException
    update changelog for fix to JENKINS-8647

    Kohsuke Kawaguchi :
    Files :

    • core/src/main/java/hudson/DNSMultiCast.java
    • core/pom.xml

    Kohsuke Kawaguchi :
    Files :

    • changelog.html

  10. jenkins-infra-bot commented on Feb 23, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 23, 2011
    Author
    eodbeeck:
    • Original comment link
    • Raw content of original comment: 
      I deployed the latest jenkins.war of 21-Feb-2011 04:02, but we still get these verbose RecordReaper errors.
The version of the included jmdns lib is 'jmdns-3.2.1-hudson-1.jar'.
      


      Was this supposed to be fixed in that version or is there anything else we can try?

    I deployed the latest jenkins.war of 21-Feb-2011 04:02, but we still get these verbose RecordReaper errors.
    The version of the included jmdns lib is 'jmdns-3.2.1-hudson-1.jar'.

    Was this supposed to be fixed in that version or is there anything else we can try?

  11. jenkins-infra-bot commented on Feb 23, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 23, 2011
    Author
    jieryn:
    • Original comment link
    • Raw content of original comment: 
      I believe this is incorporated into v1.399.

    I believe this is incorporated into v1.399.

  12. jenkins-infra-bot commented on Feb 24, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 24, 2011
    Author
    yrsone:
    • Original comment link
    • Raw content of original comment: 
      The problem still exists in Jenkins 1.398.

    The problem still exists in Jenkins 1.398.

  13. jenkins-infra-bot commented on Feb 24, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Feb 24, 2011
    Author
    yrsone:
    • Original comment link
    • Raw content of original comment: 
      Oops, my mistake ... sorry for watchers.

    Oops, my mistake ... sorry for watchers.

  14. jenkins-infra-bot
    closed this as completedon Feb 24, 2011

  15. jenkins-infra-bot commented on Mar 1, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Mar 1, 2011
    Author
    marco_rothe:
    • Original comment link
    • Raw content of original comment: 
      Fixed with 1.399, but jmdns 3.4.0 breaks the JDK 5 compatibility of hudson (see JENKINS-8914).

    Fixed with 1.399, but jmdns 3.4.0 breaks the JDK 5 compatibility of hudson (see JENKINS-8914).

  16. jenkins-infra-bot commented on Apr 2, 2013

    @jenkins-infra-bot
    jenkins-infra-bot
    on Apr 2, 2013
    Author
    markewaite:
    • Original comment link
    • Raw content of original comment: 
      Confirmed fixes long ago.

    Confirmed fixes long ago.

  17. jenkins-infra-bot
    added
    bugFor changelog: Minor bug. Will be listed after features
    imported-jira-issue
    component:core
    priority:major
    resolution:fixed
    on Nov 24, 2025

  18. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-8914]

  19. jenkins-infra-bot
    added the
    Bug
    issue type on Nov 25, 2025
  20. jenkins-infra-bot
    removed
    bugFor changelog: Minor bug. Will be listed after features
    on Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:coreimported-jira-issuepriority:majorresolution:fixed

    Type

    Bug

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions