[
https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnie McCormack updated QPID-430:
----------------------------------
Fix Version/s: (was: M4)
Moving items not being worked on afaik out of M4 Fix Version
> Message Age Alerting should not depend upon queue activity
> ----------------------------------------------------------
>
> Key: QPID-430
> URL: https://issues.apache.org/jira/browse/QPID-430
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: M2
> Reporter: Marnie McCormack
> Assignee: Aidan Skinner
> Priority: Minor
>
> Currently Message Age Alerting can be confiured such that the user might
> expect to see alerts about 'old' messages when they exceed the configured
> threshold.
> However, the alerting actually depends upon queue activity i.e.
> publication/consumption on the queue. Unfortunately, since on of the key
> purposes for the alerting is to make operate teams aware of a probable issue
> preventing message consumption this is not ideal i.e. if a publisher sends a
> message and then has no further activity and no consumer is connected, then
> no alerts are generated.
> We should implement a solution whereby alerting for message age is no longer
> tied to queue acivity (i.e. not triggered in this way) but is independent.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
