#3 Use other transport: JMS, JDBC

[Anonymous]

In a distributed application setting, it can be
interesting to dynamically connect to a running
process using log4j to generate its traces and logs.

With the current socket-based model used by ChainSaw,
it seems difficult to do such a thing. It would
require to connect to the JVM using another scheme, to
configure dynamically a SocketAppender that connects
to the ChainSaw client.

It would be easier to do such a thing if ChainSaw
could connect to a JMS publish/subscribe bus to get
log statements. An other alternative would be to
connect to a database through JDBC to retreive log
entries.