Rob,

That async appender looks quite interesting.  Does it provide any measurable benefit in normal logging?  Or do you only have because your stacktrace cleaner is heavy-weight? It does concern me that it uses an Executor with an unbounded queue which could not only cause out-of-memory exceptions, but also messages to not be saved on application shutdown (potentially).

But I do like the idea of it, as I log to log files over the network, not local disk and it's not always that fast.

David


On 13 Apr 2011, at 23:03, Robert Elliot wrote:

Just a heads up on some code that might be useful to people:

https://github.com/Mahoney/lidalia-logging

It's a couple of appenders I've found useful - basically a model for decorating other appenders (by extending DecoratingAppender) together with a couple of examples, one that cleanses Groovy stack traces so you don't get all the useless frames and one that makes any appender asynchronous with a configurable number of threads used.  There's an example logback.xml showing how to use them:

https://github.com/Mahoney/lidalia-logging/blob/master/src/main/resources/logback.xml

At some point I might try and release this as a library via Maven, but in the meantime if anyone finds them useful go ahead, and Ceki if you fancy them for Logback.  Equally if anyone has any pointers (e.g. have I reinvented the wheel?) do let me know.

Rob
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo/logback-user