activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mf <mejltill...@gmail.com>
Subject Possible loop after enabling DEBUG?
Date Fri, 02 Dec 2016 09:33:05 GMT
Hi,
I'm trying to configure ActiveMQ 5.14.1 to use secure web console with Jetty
and authenticate against Active Directory via
LDAPS.
In the process I need to debug  why it is not working but when turning on
DEBUG in log4j.properties by just
commenting in/out (as described):

*/#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

# When debugging or reporting problems to the ActiveMQ team,
# comment out the above lines and uncomment the next.

log4j.rootLogger=DEBUG, logfile, console/*



Then the webconsole does not start and it looks like a loop at startup:

*/2016-12-02 10:38:44,629 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,633 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext from java.net.URLClassLoader@17f052a3 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,640 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext from java.net.URLClassLoader@17f052a3 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,641 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,643 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,644 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,646 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext from java.net.URLClassLoader@17f052a3 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,651 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext from java.net.URLClassLoader@17f052a3 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,652 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext |
org.eclipse.jetty.webapp.WebAppClassLoader | main
2016-12-02 10:38:44,656 | DEBUG | loaded class
org.eclipse.jetty.jndi.NamingContext from java.net.URLClassLoader@17f052a3 |
org.eclipse.jetty.webapp.WebAppClassLoader | main
/*

I get this on Solaris 11 as well as on OSX 10.11.6;
On OSX I just extracted 'apache-activemq-5.14.1-bin.tar.gz' and changed the
log settings and start with './bin/activemq start'.

Is this a bug or am I missing something?

Thanks,
Mats



--
View this message in context: http://activemq.2283324.n4.nabble.com/Possible-loop-after-enabling-DEBUG-tp4719697.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message