AlertTemplateManagerBean.create/updateAlertTemplate { ... for (Resource res : type.getResources()) { // create/update alert def } } this works if there are a few thousand resources of each type...but failed when i tried to do it for a resource type with 57K committed resources of that type.
this also deals with the ability to update existing alerts, which affects our ability to test to scale.
rev4171 - reduce the xaction size for creating and updating alert templates; for QA: * crud an alert definition * crud an alert template - do all definitions get updated correctly? * make sure no errors in the server log during crud'ing
rev4650 - everything seems to work but templates take forever to be applied to actual resources. See linked issue. Please mark this one resolved when the linked issue is resolved, so i'll know when to retest.
I am seeing very poor performance when trying to disable an alert template when I have 1000 resources that the alert temlate applies to. I try to disable and the browser just spins, the work never completes.
Moving features/improvements to 1.4
Move back to 1.3 since work was actually done on this
charles, the linked issue was pushed to 1.4 on aug 26th, but you moved this one back to 1.3 on sep 1st. do we want to do this for the 1.3 timeframe or push?
I moved this issue back to 1.3 because I wanted to make sure the commits that were done in the 1.3release were tested/signed off on. Is there actually anything left to do on this task which isnt covered by http://jira.rhq-project.org/browse/RHQ-2257?
(11:18:31 AM) joseph: yeah, RHQ-905 can be resolved then
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-905