Wonder if we should just filter out our own log messages in the JMS appender, that way users can never get bitten by this problem.
On Fri, Aug 7, 2009 at 5:00 AM, Gary Tully <gary.tu...@gmail.com> wrote: > great. thanks for completing the loop on this by sharing your solution :-) > > 2009/8/7 Kinski <matthew.cosgr...@192.com> > > > > > I added the suffix to the brokerURL > > > > I.e. > > > > > log4j.appender.JMS.ProviderURL=tcp://localhost:61616?wireFormat.cacheEnabled=false > > > > but this made no difference. > > > > then finally found my needle in the haystack with this nugget of > > information.. > > > http://www.nabble.com/Log4J-ActiveMQ-JMS-Appender-td18840199.html#a19970509 > > > > > > Gary Tully wrote: > > > > > > can you run with -Dlog4j.debug (set the system property) to see where > > > the log4j configuration is coming from? > > > > > > It may be that the wireFormatNegotiator is trying to log a message > > > which is trying to start a jms connection which uses > > > wireFormatNegotiator etc. Chicken and egg. > > > logging for activemq needs to be disabled if it is used as a default > > > appender. > > > > > > > > > > Put the following in my log4j config and Hey Presto.... > > > > <!-- THIS IS CRITICAL FOR THE JMS APPENDER NOT TO FAIL --> > > <logger name="org.apache.activemq"> > > <!-- active mq logging must be disabled --> > > <level value="ERROR" /> > > </logger> > > > > -- > > View this message in context: > > > http://www.nabble.com/ActiveMQ-5-and-Log4j-JMSAppender-error-tp14622389p24860244.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > > > -- > http://blog.garytully.com > > Open Source Integration > http://fusesource.com > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://fusesource.com/
