Yes, there is a misunderstanding. I understand that the current
SocketAppender does not launch a SocketServer. I was trying to extend it
so that it does, but I was not able to extend it, do to the reasons I
suggested, and the one you also pointed out.
Since I'll probably need the code before the next release, this isn't a
critical issue for me, but in the interests of cleaning up what is there,
I believe some change should be made to the existing SocketAppender
(either make it a final class, or change a half-dozen lines of code and
make it so that it can be extended).
--
Tom Goetze
Ceki G�lc� <[EMAIL PROTECTED]>
08/05/2004 12:56 PM
Please respond to "Log4J Users List"
To: "Log4J Users List" <[EMAIL PROTECTED]>
cc:
Subject: RE: Question about implementation of SocketAppender
There is yet another misunderstanding here. SocketAppender does not launch
a SocketServer. Do you see why that changes everything in relation to your
messages?
At 09:43 PM 8/5/2004, you wrote:
>I'm thinking about extending it so that it starts its own SocketServer on
>the correct port.
>This way, even with potentially multiple JVMs running, there will only be
>one SocketServer, so there will only be one process writing to a
>particular log file (so having the SocketServer use a rolling file
>appender will be safe).
>
>This is because when there are multiple JVMs running, only 1 of the JVMs
>will be able to have its SocketServer bind to the port, the others will
>fail (quietly) but the ability to log as clients to the SocketServer will
>succeed.
>
>This avoids the hassle of writing a process to monitor a separate
>SocketServer, and re-start it if it isn't running. Of course this only
>works for multiple JVMs on the same host, but that is my current issue.
>
>Scott, were you willing to change the code? Or were you just curious?
>
>--
>Tom Goetze
>
--
Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
