You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by mf <me...@gmail.com> on 2016/12/02 09:33:05 UTC
Possible loop after enabling DEBUG?
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.
Re: Possible loop after enabling DEBUG?
Posted by mf <me...@gmail.com>.
The problem is not solved and no workaround apart from not setting the
'DEBUG' value.
It would be useful to find out my original problem trying to debug setting
up LDAPS auth for web interface logins.
I'm not sure how to file a bug or if I have to...
--
View this message in context: http://activemq.2283324.n4.nabble.com/Possible-loop-after-enabling-DEBUG-tp4719697p4719935.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Possible loop after enabling DEBUG?
Posted by sealy <10...@qq.com>.
mf wrote
> Yes,
> confirmed.
> Just setting 'log4j.logger.org.eclipse.jetty' to DEBUG breaks web console.
>
> Looks like same problem with 5.13 and 5.11.3, have not checked further.
>
> Mats
hi, i've met the same problem with you. Please tell me the problem solved or
not, and how to solve it. Thank you.
--
View this message in context: http://activemq.2283324.n4.nabble.com/Possible-loop-after-enabling-DEBUG-tp4719697p4719932.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Possible loop after enabling DEBUG?
Posted by mf <me...@gmail.com>.
Yes,
confirmed.
Just setting 'log4j.logger.org.eclipse.jetty' to DEBUG breaks web console.
Looks like same problem with 5.13 and 5.11.3, have not checked further.
Mats
--
View this message in context: http://activemq.2283324.n4.nabble.com/Possible-loop-after-enabling-DEBUG-tp4719697p4719767.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Possible loop after enabling DEBUG?
Posted by Tim Bain <tb...@alumni.duke.edu>.
Mats,
That's definitely an infinite loop: look at thread 3079.
If you configure org.eclipse.jetty.webapp.WebAppClassLoader at INFO but
everything else at DEBUG, does the problem disappear?
Tim
On Dec 5, 2016 2:38 AM, "mf" <me...@gmail.com> wrote:
> Thanks for reply Tim,
> following is a list of commands and output so should make it easy to
> reproduce,
> I'm not too used to debug java so list all output from jstack;
>
> Mats
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Possible-loop-after-enabling-DEBUG-tp4719697p4719746.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: Possible loop after enabling DEBUG?
Posted by mf <me...@gmail.com>.
Thanks for reply Tim,
following is a list of commands and output so should make it easy to
reproduce,
I'm not too used to debug java so list all output from jstack;
Mats
--
View this message in context: http://activemq.2283324.n4.nabble.com/Possible-loop-after-enabling-DEBUG-tp4719697p4719746.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Possible loop after enabling DEBUG?
Posted by Tim Bain <tb...@alumni.duke.edu>.
Can you run jstack to see if you are indeed in an infinite loop?
Also, can you confirm that everything worked correctly before you enabled
DEBUG?
Also, can you please describe the symptoms that led you to say "webconsole
does not start"?
On Dec 2, 2016 2:46 AM, "mf" <me...@gmail.com> wrote:
> 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.
>