Absolutely right!!! The pattern was:

      <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-40([%thread] %C{0} $logger) %msg%n</pattern>

Instead of

      <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-40([%thread] %C{0} %logger) %msg%n</pattern>

Now I'll try filtering based on the logger approach!

Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (R&D)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes
(56-2) 335 2461
gvasquez@altiuz.cl
http://www.altiuz.cl
 


El 30-05-2012, a las 16:28, ceki escribió:


The pattern %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n" does not match the output sent in your message. You probably have another config file lying around with $logger instead of %logger in the pattern.

On 30.05.2012 22:14, Gonzalo Vasquez wrote:
Strange, but I'll check as I'm getting the following kind of messages:

16:09:35,447 INFO [STDOUT] 2012-05-30 16:09:35.447 [RMI TCP
Connection(4)-127.0.0.1] QueryResultImpl $logger retrieved ScoreNodes in
0 ms (0)

[snip]

Using this pattern:

<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>


So it seems that $logger is the logger name, isn't it?


--
Ceki
http://twitter.com/#!/ceki
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-user