You can pass -Dlog4j.debug=true on your command line to find out where log4j is picking up it's configuration and how it's parsing it.
On Mon, May 9, 2011 at 6:44 AM, degenaro <[email protected]> wrote: > Thanks for your reply. I think one of my problems is that I don't know where > the log4j.properties file that needs to be modified is! > > My application code is using log4j too. Without success, I tried updating > its log4.properties file thus: > > # Set root logger level to INFO and its only appender to A1. > log4j.rootLogger=WARN, A1 > > # A1 is set to be a ConsoleAppender. > log4j.appender.A1=org.apache.log4j.ConsoleAppender > > # A1 uses PatternLayout. > log4j.appender.A1.layout=org.apache.log4j.PatternLayout > log4j.appender.A1.layout.ConversionPattern=%d %m%n > > log4j.logger.org.apache.activemq.transport.failover.FailoverTransport.level=ERROR > > Lou. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Hide-ActiveMQ-log4j-messages-tp3506729p3508906.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
