[JIRA] [core] (JENKINS-6697) Too many multicast dns answers
Daniel Beck resolved JENKINS-6697 as Incomplete Too many multicast dns answers Resolving as 'Incomplete' after no response to comment asking for updated information in over two weeks. Due to the age of this issue, please file a new issue if this still occurs on recent Jenkins versions. Change By: Daniel Beck (14/Jun/14 3:14 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6697) Too many multicast dns answers
Daniel Beck commented on JENKINS-6697 Too many multicast dns answers Has anyone observed this in a recent version of Jenkins? In mid 2011, jmDNS 3.4.0 was integrated into Jenkins, maybe it's resolved since then? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
