Adding web console to MQ broker doesn't show queue created by pinger demo

[komododave]

I set up the fmc pinger example and it runs fine.

The MQ broker it's sending messages to has the mq-web-console feature added.

However, when I access the Fuse MQ web console via host:8181/activemqweb the PING.SEND queue isn't visible.

Should it be, or is additional configuration required?

I'd like to be able to inspect the messages enqueued and dequeued.

[stlewis]

Can you see via FMC if there's more than one broker instance running?  You'd go to the container detail page for the container running MQ, then click on the Fuse MQ button.  I've seen cases where the MQ web console starts it's own broker instance.

[komododave]

Yes you're absolutely right Stan. I can see a web-console broker is listed in FMC in addition to the broker of same name as the container.

And loading Fuse MQ Console states:

Welcome to the Fuse MQ Console of web-console

i.e. doesn't show anything because it's monitoring the unused web-console broker.

Is this a bug? Is there a workaround I can use for now?

Sincere thanks for your time, I do appreciate your informative responses.

[stlewis]

Asked around about this and currently the activemq web console isn't configured via the OSGi ConfigAdmin (ENTMQ-138).  So what you have to do in the meantime is configure the web console via system properties as outline on this page under "Configure using System-Properties".

You'll also want to edit the "mq-base" profile, go to the "Configuration" tab and click on the "broker.xml" and set what port the broker will come up on, that way you know what port to configure the web console to use.

[komododave]

Thank you for this information Stan. I'll follow your instructions now.

[komododave]

By the way, wouldn't you agree the mq-web-console shouldn't include a broker itself by default anyway?

I just tried extending profile mq-base and adding the mq-web-console feature, but its broker isn't set up in the same way as that of the mq profile, sadly. So no pinger example messages are enqueued or dequeued. Shame, that would have been an easy fix!

[komododave]

This worked like a charm once I added the system properties via FMC and changed the openwire port in broker.xml as you indicated. Many thanks.