[
https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie updated QPID-430:
--------------------------------
Assignee: Aidan Skinner (was: Martin Ritchie)
Status: Open (was: Ready To Review)
MockAMQQueue uses @Override on an interface this is a Java 6 features
'housekeeping.expiredMessageCheckPeriod' is no longer accurate. Should
deprecate this name and use one more representative.
Users changing the alert notification period may not realise that they need to
change the 'expired message check period' for that to have an effect.
> 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
> Fix For: M5
>
>
> 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.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
