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 [EMAIL PROTECTED] 2002-07-30 20:48 ------- I have to state before anything else, that the use of the SocketAppender is a necessity for us, as several applications are writing to similar log files. We had big problems in the past when all those applications were opening the same file for writing. I agree in general with your comments, but in our case a small modification would save us from loosing ANY message. What you suggest demands more work and may be memory consuming (when do you stop buffering messages?). Both solutions are fine by me, as long as we do something for it. I can even suggest one more solution: keep the current thread that tries to connect to the server, but increase the sleep time every time you fail. Then, I can put a very small sleep for the first effort - which in my case will immediately succeed - and still not get thousands of errors when the server is REALLY down. One just final remark: concerning performance, if someone considers it a bottleneck, then he may well use the AsynchAppender to offload the main application. In our case, it would still not solve the problem. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
