Using 3.4.1 there appears to be a network flood issue with JmDNS. Attached is a quick tcpdump which illuatrates what I\'m talking about (this is using: tcpdump -n -i en0 udp port 5353 > pcap.txt ). The issue can saturate a 100MBit link.
The network topology is as follows:
Our app uses JMDns to \'know\' about other instances of itself running on our network. This means that there are about 40 registered service listeners on different computers *and* multiple instances on a terminal services machine (which has a single IP)
I\'ve put a very crude (horrible!) hack in to mitigate the issue (basically doesn\'t allow JmDNS to .send(DNSOutgoing) duplicate packets for at least 3 seconds), and this appears to fix the issue without degrading functionality