Based on code changes in TCLFilter, it looks like they changed how it decides if the even
should be logged. Now, if acceptOnMatch is true and the TCL does not match, it returns
NEUTRAL result instead of a deny RESULT. NEUTRAL means that this filter could not decide
one way or the other and the next filter in line should check. According to
AppenderSkeleton (in log4j), if there are no other filters returning a NEUTRAL result is
the same as returning ACCEPT.
So yes, it looks like someone broke(?) the code, probably in an effort to fix a bug that
someone else issued that said that they could not chain filters.
There is a org.apache.log4j.varia.DenyAll filter. You could try adding that to the filter
chain. (Now I get it, the last filter in the chain should always be a DenyAll, this way is
any of the other filters do not specifically ACCEPT the event, the last filter denies
it.)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204442#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...