Hi,
logQuery bean example in activemq.xml:
<bean id="logQuery"
class="org.fusesource.insight.log.log4j.Log4jLogQuery"
lazy-init="false" scope="singleton"
init-method="start" destroy-method="stop">
</bean>
does not work in combination with debug setup on log4j.properties.
Test case:
1) No debug - everything is working
i do not change anything in default config and startup 5.9.0 using
./bin/activemq start
everything works as expected.
2)I do not change anything only set debug logging as advised by uncomenting
line in ./conf/log4j.properties
#log4j.rootLogger=DEBUG, logfile, console
and comment out following lines:
log4j.rootLogger=INFO, console, logfile
log4j.logger.org.apache.activemq.spring=WARN
log4j.logger.org.apache.activemq.web.handler=WARN
log4j.logger.org.springframework=WARN
log4j.logger.org.apache.xbean=WARN
log4j.logger.org.apache.camel=INFO
log4j.logger.org.eclipse.jetty=WARN
and try to start the broker.
In activemq log I get infinite loop of:
2013-11-12 16:12:14,338 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,341 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,344 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,351 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet from
java.net.URLClassLoader@6719dc16 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,363 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet from
java.net.URLClassLoader@6719dc16 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,365 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,374 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet from
java.net.URLClassLoader@6719dc16 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,391 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet from
java.net.URLClassLoader@6719dc16 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,394 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,398 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,406 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet from
java.net.URLClassLoader@6719dc16 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,446 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet from
java.net.URLClassLoader@6719dc16 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,456 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,463 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet from
java.net.URLClassLoader@6719dc16 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,482 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet from
java.net.URLClassLoader@6719dc16 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,485 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,488 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2013-11-12 16:12:14,491 | DEBUG | loaded class
org.eclipse.jetty.servlet.DefaultServlet |
org.eclipse.jetty.webapp.WebAppClassLoader | main
and broker is never started.
Can anyone confirm debug works together with, because as soon as I remove it
everything works fine even in debug mode:
<bean id="logQuery"
class="org.fusesource.insight.log.log4j.Log4jLogQuery"
lazy-init="false" scope="singleton"
init-method="start" destroy-method="stop">
</bean>
Michal
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-example-configuration-does-not-work-with-debug-set-in-log4j-in-5-9-0-tp4674218.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
