Monitoring Broker Redelivery with ActiveMQ -


We have configured our active MQ broker with this Broker Re-delivery plugin using this configuration.

  & lt; RedeliveryPlugin fallback-backed liter = "true" dispatch TODLqIfMaxRetriesExpecteded = "true" & gt; & Lt; RedeliveryPolicyMap & gt; & Lt; RedeliveryPolicyMap & gt; & Lt; RedeliveryPolicyEntries & gt; & Lt; / RedeliveryPolicyEntries & gt; & Lt ;! - Fallback policy for all other destinations - & gt; & Lt; DefaultEntry & gt; & Lt; Redelivery Policy Maximum Redeliveries = "15" UsageEnginebackbackoff = "True" Initial ReddivalireDial = "5000" UsageRightVision = "True" Backoffimultiplier = "5" Maximum Reddelivery = "93600000" /> & Lt; / DefaultEntry & gt; & Lt; / RedeliveryPolicyMap & gt; & Lt; / RedeliveryPolicyMap & gt; & Lt; / RedeliveryPlugin & gt;  

The plugin expects the removal of the unsuccessful message from the queue and retrying at the specified interval.

The problem that is coming up now is that we have to monitor how many messages are waiting for each queue to retry, because they are not waiting for normal queue monitoring Will appear. I could not find anything in the JMX tree for the ActiveMQ related to the DealerPlugin tree.

The message is stored in the Job Schedulerstor which is a separate shop from the usual AMQ Keyadi or JDBC Store. There is less visibility but this should be an MBN. You can get some information through JMX or you can get information by sending a JMS message with a special header set. There is an article on JMS style administration.


Comments

Popular posts from this blog

Member with no value in F# -

java - Joda Time Interval Not returning what I expect -

c# - Showing a SelectedItem's Property -