Alert with multiple conditions does not honor metric collection interval

Issue

• An alert that should be fired when ALL conditions are fulfilled may be triggered although it's conditions are not fulfilled at the same time;
• We defined an alert that should be fired when ALL conditions are fulfilled where conditions are:
  • Metric Value Threshold [Inflight Exchanges > 0.0]
  • Metric Value Threshold [Exchanges Completed per Minute = 0.0]
• Sometimes we get false alarms where condition1 and condition2 timestamps seem to differ more then 20 minutes (metric collection interval is 20 minutes for both measurements) - sometimes it's been more then few hours difference;
• We got the following alert:

Subject: [ALERT] priority of [Medium] for alert [Alert - Camel Route Stalled] on resource [file-to-jms-route Route]

The resource file-to-jms-route Route has generated the following alert:

------------------------------------------

Resource Name    : file-to-jms-route Route
Alert Name       : Alert - Camel Route Stalled
Alert Severity   : Medium
Alert Date/Time  : Mon May 25 15:25:43 BST 2015
Conditions: 
  - Condition 1: Inflight Exchanges > 0.0
  - Date/Time: 2015/05/25 15:25:28 BST
  - Details: 1.0

  - Condition 2: Exchanges Completed per Minute = 0.0
  - Date/Time: 2015/05/25 14:27:55 BST
  - Details: 0.0


------------------------------------------

Resource Ancestry:

stever.fab.redhat.com [Platforms, Linux]
  JBoss Fuse{/home/ingo/jboss-fuse-6.1.0.redhat-379} JBoss Fuse [root] [JBossFuse, JBoss Fuse Container]
    org.jboss.quickstarts.fuse.jms jms-example-context Camel Context 2.12.0.redhat-610379 [Camel, Camel Context]
        file-to-jms-route Route [Camel, Camel Route]

although "Exchange Completed per Minute" was not 0.0 at the time when "Inflight Exchanges" was > 0.0.