You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2004/05/12 16:51:52 UTC
DO NOT REPLY [Bug 28927] New: -
SocketNode cannot never send socketClosedEvent.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28927>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28927
SocketNode cannot never send socketClosedEvent.
Summary: SocketNode cannot never send socketClosedEvent.
Product: Log4j
Version: 1.3alpha
Platform: All
OS/Version: All
Status: NEW
Severity: Major
Priority: Other
Component: Other
AssignedTo: log4j-dev@jakarta.apache.org
ReportedBy: rmarbeck@free.fr
The test "if (listener != null)" in run method of SocketNode, is always false
because listener is not initialized in this class.
Consequently SocketHubReceiver, for example, is not triggered when SocketNode is
closed.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org