logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Udstrand" <...@completeis.com>
Subject Re: [SUBMIT] ServerSocketAppender.java
Date Fri, 08 Mar 2002 02:40:45 GMT

    I took a different approach to the same problem.  In my case I wrote a
UDPMulticastAppender for log4j and modified chainsaw to read and display
these messages.  Advantages are that anyone on the subnet is able to join
the multicast group and view the server log messages.  In our particular
case we have clustered servers (Weblogic) that are all able to broadcast to
a single port to be read and combined by Chainsaw.

    I am in the process of adding the ability to change the port and the
multicast address in Chainsaw so that I am able to switch between our
dev/test/vendor/prod areas and watch the system log messages in real time
without having to stop and reconfigure Chainsaw.

    Since UDP is not secure I plan on adding some level of encryption to the
packets to prevent just anyone from viewing the data in a prod environment.

    I am not sure that I am quite ready to distribute this Appender on this
list but if there is enough interest I will.


----- Original Message -----
From: "Mark Womack" <mwomack@bevocal.com>
To: "Log4j-Dev (E-mail)" <log4j-dev@jakarta.apache.org>
Sent: Wednesday, March 06, 2002 7:14 PM
Subject: [SUBMIT] ServerSocketAppender.java

> Enclosed is a new appender, ServerSocketAppender.java.  Please consider it
> for inclusion in the log4j project.  If there are concerns with the source
> or design, please let me know so I can correct them.
> ServerSocketAppender borrows heavily from the SocketAppender, and the code
> will look remarkably the same.  But instead of connecting to a remote
> socket, ServerSocketAppender creates a ServerSocket object and then
> any number of connections by remote clients.  When a log event is to be
> appended, the event is sent to the set of current connections.  If an
> is encountered sending the event, the connection is dropped.  No attempt
> made to reconnect since it is the responsibility of the client to make the
> connection to begin with.
> Why ServerSocketAppender?  If you have a group of developers accessing the
> same logging event source server, each one will need their own
> SocketAppender defined to pump log events to their client.  Add another
> developer, add another SocketAppender.  With ServerSocketAppender, you set
> up the appender once, let everyone know the port number and then have
> clients connect to it when ever they want to.  It is always there, ready
> send you log events.  It also conserves socket ports since you only need
> port instead of a port per SocketAppender.
> I am working on modifications to Chainsaw so that it can actively initiate
> connections with ServerSocketAppenders instead of only passively accept
> connections from SocketAppenders.  Then you could use it to connect to any
> number of sources.
> If you have any questions, or concerns, please let me know.
> thanks,
> -Mark


> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>

View raw message