Bug 43874 - SocketHubAppender should expose actual port in use to extending classes
SocketHubAppender should expose actual port in use to extending classes
Status: RESOLVED FIXED
Product: Log4j
Classification: Unclassified
Component: Appender
1.2
Other other
: P2 enhancement
: ---
Assigned To: log4j-dev
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2007-11-15 11:04 UTC by Curt Arnold
Modified: 2008-07-03 15:51 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Curt Arnold 2007-11-15 11:04:31 UTC
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.
Comment 1 Curt Arnold 2007-11-15 11:14:00 UTC
Committed a pass in rev 595394.

Previous discussion in http://marc.info/?l=log4j-dev&m=119515188302606&w=2
Comment 2 Thorbjørn Ravn Andersen 2008-07-03 14:32:05 UTC
Is the issue still present, or can this issue be closed?
Comment 3 Paul Smith 2008-07-03 15:51:27 UTC
I believe we knocked this off recently and is part of the 1.2.16-SNAPSHOT (it's in the change.xml).