Bug 571908
Summary: | If a user assigns a misconfigured Mobicents Alert Sender Plugin to an Alert, the Alert will not fire | ||||||
---|---|---|---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Steve Salevan <ssalevan> | ||||
Component: | Alerts | Assignee: | Heiko W. Rupp <hrupp> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Sudhir D <sdharane> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | unspecified | CC: | ckannan, cwelton | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 2.4 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-08-12 16:55:15 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 565635 | ||||||
Attachments: |
|
Description
Steve Salevan
2010-03-09 20:03:00 UTC
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. |