How to repeat: On the RHQ Server resource, set the Metric Collection Interval for "Active Thread Count" to 1 minute. Now create an alert on the same resource, with the condition "Active Thread Count > -1". This alert should always fire, and with the collection interval set to 1 minute, the alert should fire within 1 minute. The problem is it doesn't. It takes anywhere from 15 to 90 minutes. Thereafter, it fires every minute as expected, but the problem is the delay before the first firing.
perhaps this has something to do with the need for the agent to "connect" to the server in order to load the alert cache. If for some reason the server fails to load the alert cache for the agent, alerts don't fire. That's the only reason why I would think alerts wouldn't fire for a long period.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2448
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
mass move to rhq_chainsaw tracker bug
moving any remaining Alert related bugs to rhq_chainsaw
This bug has now been triaged by Chainsaw on 2/18. The expectation is the bug to be addressed by the end of sprint06 roughly 3/10/10.
This bug is blocking ALL automated alert testing. Needs to be addressed ASAP.
commit 546f7dbcc30ecb0666f49958f275baac3c640151 fix for newly created event/measurement-based alerts not firing * was previously trying to set agent status bit by alert definition id via pure JPQL * however, at the time the JPQL is executed, the alert definition hasn't been persisted yet * fix was to correlate the cache reload to resourceId instead, which is only required in the CREATE case * added new method to StatusManagerBean called updateByResource to handle this new path * updated logic in notifyAlertConditionCacheManager to switch on the AlertDefinitionEvent appropriately * added more debug-level logging
qa -> cwelton
QA Verified... alerts now begin to fire immediately. Great!
Mass-closure of verified bugs against JON.