Description of problem: If a user assigns a misconfigured Mobicents Alert Sender Plugin to an Alert, the Alert itself will not fire. Version-Release number of selected component (if applicable): RHQ, 5/9 git pull, master branch How reproducible: Always Steps to Reproduce: 1. Incorrectly configure the Alert:Mobicents server-side plugin 2. Add the Mobicents Alert Sender Plugin to an alert which is currently firing Actual results: Alert stops firing Expected results: Alert continues to fire, including any related errors in alert fire report Additional info:
Created attachment 398915 [details] resulting traceback taken from rhq-server-log4j.log
Steve, do you have any more details on how to reproduce - what was the misconfiguration you mention? I did configure mobicents with a non-available server and get the following in the log (which is expected): 15:31:29,780 INFO [MobicentsSender] Mobicents alert [VOICE] to baseUrl [http://localhost:8080/mobicentscall?alertId=11203&tel=sip:1345%40localhost] with message: alertText=Alert on resource snert-e. Cause is - Condition 1: Free Memory value changed - Date/Time: 2010/03/22 15:31:15 CET - Details: 160.8MB 15:31:29,780 WARN [MobicentsSender] Notification via VoIP failed: java.net.ConnectException: Connection refused 15:31:29,780 INFO [AlertManagerBean] SenderResult{message='Sending failed Connection refused', state=FAILURE, emails=[]} But no stack trace.
I see this as "won't fix" - users that misconfigure a plugin can not expect it to work.
I agree... however, the Alert itself should fire. I'll retest this today and see if the original issue still reproduces.
I verified that with _correct_ configuration, alerts are firing as expected. Also, considering comments#3 and #4, I'm marking this bug as verified.
Mass-closure of verified bugs against JON.