You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2007/03/22 15:21:32 UTC
[jira] Created: (QPID-430) Message Age Alerting should not depend
upon queue activity
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
Priority: Minor
Fix For: M2
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.
[jira] Assigned: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner reassigned QPID-430:
----------------------------------
Assignee: Martin Ritchie (was: Aidan Skinner)
> 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: Martin Ritchie
> 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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ 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: M2)
M3
Moving unresolved JIRAs from M2 to M3, in preparation for M2 release
> 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
> Priority: Minor
> Fix For: M3
>
>
> 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.
[jira] Commented: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611615#action_12611615 ]
Aidan Skinner commented on QPID-430:
------------------------------------
This should be wired into the housekeeping thread.
> 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
> Priority: Minor
> Fix For: M3
>
>
> 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.
[jira] Updated: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ 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:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner reassigned QPID-430:
----------------------------------
Assignee: Martin Ritchie (was: Aidan Skinner)
MockAMQQueue is a concrete class, not an interface. :)
s/expiredmessage// old name is used if that isn't present, then the default.
> 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: Martin Ritchie
> 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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ 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: M5
> 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
> 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.
[jira] Assigned: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner reassigned QPID-430:
----------------------------------
Assignee: Aidan Skinner
> 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
> Fix For: M3
>
>
> 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.
[jira] Updated: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-430:
----------------------------------
Priority: Major (was: Minor)
> 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.
[jira] Updated: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner updated QPID-430:
-------------------------------
Status: Ready To Review (was: In Progress)
> 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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner updated QPID-430:
-------------------------------
Status: Ready To Review (was: In Progress)
> 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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-430) Message Age Alerting should not depend
upon queue activity
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ 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.