FYI Guillaume,
I continued this discussion on the OPS4J mailing list:
http://www.mail-archive.com/general@lists.ops4j.org/msg12287.html
/Bengt
2012/1/30 Bengt Rodehav be...@rodehav.com
A moment ago I thought I had solved the problem since I noticed that I had
written bunde.name:... instead
I have the following configuration in my org.ops4j.pax.logging.cfg:
*# Per bundle log at INFO level*
*log4j.appender.bundle=org.apache.log4j.sift.MDCSiftingAppender*
*log4j.appender.bundle.key=bundle.name*
*log4j.appender.bundle.default=karaf*
The filter support has been added in pax-logging.
Have a look at
https://github.com/ops4j/org.ops4j.pax.logging/blob/master/pax-logging-service/src/main/java/org/apache/log4j/PaxLoggingConfigurator.java
You may very well be right that the order isn't kept, which would
definitely be a bug.
On
Actually, the filters support is built into log4j, but if there's
really a problem we can always fix it in pax-logging until the patch
is released in log4j.
On Mon, Jan 30, 2012 at 10:21, Guillaume Nodet gno...@gmail.com wrote:
The filter support has been added in pax-logging.
Have a look at
No, the support has been added in log4j:
http://svn.apache.org/viewvc?view=revisionrevision=821430
On Mon, Jan 30, 2012 at 10:30, Bengt Rodehav be...@rodehav.com wrote:
Hello Guillaume,
Doesn't the filter support in log4j require XML configuration (not
properties file)? If so, then I
Looking at the log4j code, it seems the filters are ordered using
their ids, so in your case accept and deny.
So I think the order should be ok. Can you try changing their name so
that the order would be reversed ?
On Mon, Jan 30, 2012 at 11:09, Bengt Rodehav be...@rodehav.com wrote:
OK - I
I also tried the following:
log4j.appender.bundle_trace.filter.a=org.apache.log4j.varia.StringMatchFilter
log4j.appender.bundle_trace.filter.a.StringToMatch=bunde.name:
org.apache.camel.camel-core
log4j.appender.bundle_trace.filter.a.AcceptOnMatch=false
I didn't use a DenyAllFilter in this case.
Have you tried matching on something more simple such as camel ?
The StringToMatch filter simply looks for the string to be in the
rendered event so maybe none of you events contains
bunde.name:org.apache.camel.camel-core
On Mon, Jan 30, 2012 at 11:52, Bengt Rodehav be...@rodehav.com wrote:
I
A moment ago I thought I had solved the problem since I noticed that I had
written bunde.name:... instead of bundle.name: That would have
explained everything but unfortunately I still can't get it to work after
having corrected my spelling.
Using the org.apache.camel logger won't help me
