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:/
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.
Hi,
maybe just copy-paste error or you have a typo with 'andomize', it should be
'randomize' (?) :)
Maybe off topic, but I think a network of brokers setup is sweet, running
two brokers with independant storage, in case one broker goes down and comes
back, the brokers would be able to pass message
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-tp4719697p471974
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=IN
