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 2002/07/30 20:27:22 UTC
DO NOT REPLY [Bug 11285] -
SocketAppender fails to reconnect immediately
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11285>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11285
SocketAppender fails to reconnect immediately
------- Additional Comments From mwomack@apache.org 2002-07-30 18:27 -------
I think it will be very tough to guarantee that log messages will not
get "dropped" when a connection is down/lost. You don't want to tie up the
appender to reconnect when it is trying to append the event because that will
affect the performance of the caller. I think that to better guarantee the
delivery of log messages and still maintain good performance one would need to
create a buffer where messages get stored while the connection is down. Then,
when the connection comes back up, the contents of the buffer get sent.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>