bugzilla | 25 Feb 04:25 2012

DO NOT REPLY [Bug 52765] New: ZeroConf does not work


             Bug #: 52765
           Summary: ZeroConf does not work
           Product: Log4j
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: chainsaw
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: charles.c.strahan <at> gmail.com
    Classification: Unclassified

There are a couple aspects of this problem for me to address, so here we go.
This report is based on the latest trunk of Chainsaw as of earlier today
(should be revision 1178454), on Ubuntu 11.04.

First of all, the old 2006 binary (found here:
http://logging.apache.org/chainsaw/download.html) is capable of detecting
appenders registered with a type of _log4j._tcp.local. This is no longer so in
the latest revision (although it doesn't really hold me back, personally). I
think (per this ticket:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48907) that
_log4j._tcp.local. was supposed to be supported for backwards compatibility
with the ZeroConfSocketHubAppender.

Secondly, I don't think that the ZONEs are formatted correctly for the other
appenders/receivers, nor in ZeroConfPlugin.java. For example, I believe that


should be:


Note the missing `._udp'. I'm not terribly familiar with
ZeroConf/mDNS/Bonjour/whatever, but I do believe that the protocol (tcp or udp)
is required as part of the registration. Concretely, if I make the suggested
change and then try the following ruby code, the appender is correctly
configured in Chainsaw:

  require 'dnssd'

  name = "My log4j appender"
  type = "_log4j_xml_udp_appender._udp"
  domain = nil
  port = 3689

  DNSSD.register(name, type, domain, port)

  puts "Press enter to exit . . ."

If I wasn't clueless about Java development, I'd give fixing this a shot...



Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.