ActiveMQ Monitoring

Question

Hi again,

we are currently implementing a microservice that we connect to the Yuuvis ActiveMQ via JMS. We consume the topic "indexDataChanged" and use a durable subscriber with a retry policy.

On our DEV environment we had the situation that our Micorservice received/consumed all JMS messages again after restarting the "yuuvis RAD service manager".

We could not reproduce the problem so far. But we want to make sure that this problem does not affect us on production.

Therefore we would like to monitor the ActiveMQ.

• Is the ActiveMQ Web Console active and if not, could it be activated?
• Is it possible to monitor the AMQ with e.g. https://hawt.io/ via JMX (or Jolokia REST interface)?

Many thanks and best regards
Martin

Answer 1

Hi Martin,

yes, it is possible to connect to Hawtio. To do so, you have to start Hawtio locally and add the /manage path when the connection is established.

Best regards,
Anna

Answer 2

Hello Martin,

if you just want to monitor the number of messages in each queue, you can use the swagger-ui interface or the corresponding rest-ws endpoint:
http://service-manager-ip:7311/swagger-ui.html
-> click on the drop-down box at the top and select "messaging-api"
-> click on "api-controller"
-> click on "/api/cpb/browsequeues"
-> click on "Try it out!" button.
In the response body section you will see each existing queue with its current number of contained messages. Also you will see the exact url - for programmatic use.

Best regards
Nicolai

Comments

Hello, how can I emty a Queue? The swagger itself does not explain it and it does not work with what I tried it

---

Hi Enno, you can use the /api/cpb/emptyqueue endpoint.
If you don't have the newest 9.16 or 10 hotfix then the swagger-ui might show "arg0" instead of "queue" as the parameter name. In that case copy the url shown and execute the request in the browser using queue=<queuename> (instead of arg0=<queuename>) as path-parameter.
Alternatively you can stop the messaging-service and delete the entire <service-manager-data>\messaging-broker\KahaDB\queue#3a#2f#2f+<queuename> folder. Then restart the messaging-service.

Best regards
Nicolai