The port for a SocketHubAppender may be specified as zero which results in the appender listening on some free port. The zeroconf companion has an extended SocketHubAppender which advertises the appender, but has no means of determining the actual port in use in the case to appropriately advertise. This bug will modified SocketHubAppender to allow zeroconf to determine the port in use.
Committed a pass in rev 595394. Previous discussion in http://marc.info/?l=log4j-dev&m=119515188302606&w=2
Is the issue still present, or can this issue be closed?
I believe we knocked this off recently and is part of the 1.2.16-SNAPSHOT (it's in the change.xml).