I need a remote logging configuration that can guarantee delivery. If the server is down, I need the client to queue up the log events until it is back up. However, I don't believe Log4j does this at present. SocketAppender has an ObjectOutputStream that handles the writing, but if it is null (connection is dead), SocketAppender simply drops the log messages on the floor without saying anything. This behavior is unacceptable in a robust system in which log messages are crucial data.
I tried to use AsyncAppender, since it employs a buffer, but all it does is take the event off the queue and pump it to all attached appenders. So, if the socket is still down, SocketAppender will ignore the event and AsyncAppender won't care. It won't go back on the queue for a later time. First, could a developer who knows this code well respond? Second, is there another solution. In an enterprise scenario, we must be able to provide reliable delivery. Thank you Daniel Hannum ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions Health Services Corporation and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you -- To unsubscribe, e-mail: <mailto:log4j-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:log4j-dev-help@;jakarta.apache.org>
