Something is very odd.  This error:


Should not be reported when hitting the main Queue page on the broker
because that page is iterating existing destinations in the broker, unless
the broker is starting up with JMX disabled.

Is it possible the wrapper is causing a different broker config file to be
used?  If that's hard to tell, try making the config file invalid (i.e. put
random text in the file) and start the broker with the wrapper.

Another check - once the broker starts with the wrapper, is it possible to
connect JConsole of VisualVM to the broker?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677996.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to