ActiveMQ Web Console

[woggle23]

Morning all

I've recently started playing with Fuse Fabric. My first attempt was to follow a demonstration which utilised the following containers:

Root (fabric registry) running on Windows platform

ssh container created on linux-vm-1, running the "mq" profile

ssh container created on linux-vm-2, running the "camel" and "example-camel" profiles

These appear to work as expected. However, I wish to view the activemq web console. I did hope that this would be accessible via the Root container, as it controls the activemq broker(s). And I noted that the config on the root contained a default broker, so whether I could access the broker running on linux-vm-1 or not, I expected to be able to view the broker running on root. When attempting to access the webconsole, via http://localhost:8181/activemqweb, I was presented with an "Authentication failed" error (full stack trace in the attached file), when no login credentials had been requested. Note, I had installed the "activemq-web-console" and "mq-web-console" (What are the differences in these two features? I note there was a ticket raised on this; http://fusesource.com/issues/browse/ENTESB-150).

Any idea why I'm not able to view the console?

In addition, I tried to create a new profile which would install the activemq-web-console on linux-vm-1, following the guidance suggested in the documentation listed below:

http://fusesource.com/docs/esbent/7.0/amq_admin/FMQAdminConsoleLocal.html

The outcome when viewing "container-list" from root was:

FuseESB:karaf@root> container-list

broker1                        1.0       true    mq-console                     error - java.net.MalformedURLException: no protocol: mq-web-console

        at java.net.URL.(URL.java

A full stack trace, copied from the linux-vm-1 log is in the attached file.

I note that when I connect to the two remote containers that they have none of the "features" commands available - is this causing an issue? How are the features listed in the profile installed in the target container? I assumed the remote container itself would install all necessary features?

Any ideas how I resolve these issues and progress?

Many thanks

Matt

[stlewis]

It looks like you added mq-web-console to the profile as a bundle accidentally instead of a feature, double-check how you've configured the profile using profile-display, mq-web-console should show up as a feature.  Also be sure that "mq" is a parent of your new profile, and when you ran container-change-profile you specified both "mq" and "mq-web-console" as profiles to set on the container.  And you're correct, you'd want to configure the mq web console on the container where the broker is running to view that broker's statistics.

[woggle23]

Many thanks for your reply. You were right, the mq-web-console had been added to the profile as a "fab" and not a "feature". Updated the profile as suggested, and now have access to the remote containers mq-web-console. However, there is an issue - I updated the remote containers profile as follows:

container-change-profile broker1 mq-console.

When attaching to http://:8181/activemqweb, there were no connections, topics etc displayed. After "connecting" to the remote container I noted that 2 brokers had been created; "web-console" and "broker1". And the Camel route, running in the other remote container, had connected to "broker1". Any help on the following questions were be much appreciated:

Any idea why 2 brokers were created?

Why does mq-web-console only have information regarding one of the brokers (web-console)?

Cheers

Matt