Bug 607548 - Alert notification: for Resource Operations is failing with NPE
Summary: Alert notification: for Resource Operations is failing with NPE
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Alerts
Version: 3.0.0
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Joseph Marques
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks: jon24-alert-notify 602788
TreeView+ depends on / blocked
 
Reported: 2010-06-24 10:57 UTC by Sudhir D
Modified: 2010-08-12 16:46 UTC (History)
1 user (show)

Fixed In Version: 2.4
Clone Of:
Environment:
Last Closed: 2010-08-12 16:46:54 UTC
Embargoed:


Attachments (Terms of Use)
Resource operation alert notification failure (145.80 KB, image/png)
2010-06-24 10:57 UTC, Sudhir D
no flags Details

Description Sudhir D 2010-06-24 10:57:11 UTC
Created attachment 426524 [details]
Resource operation alert notification failure

Description of problem:
Alert notification for any of the Resource Operations throw NPE when clicked on Save.

Version-Release number of selected component (if applicable):
jon-server-2.4.0.GA_QA Build# 42.

How reproducible:
Always

Steps to Reproduce:
1.  Create an alert for a jboss as server, i.e., RHQ
2.  Type: Resource Operations
    Resource Selection Mode: This Resource
3.  Click Save.
  
Actual results:
Failed to save alert notification Cause: java.lang.NullPointerException:null
is thrown on the screen.

Expected results:
The page should automatically refresh giving the next option and when clicked on save it should save the settings.

Additional info:
Screenshot attached.

Comment 1 Joseph Marques 2010-06-24 12:20:57 UTC
Sudhir, in the future please also check your server log files and post any stack traces you see to the case as well.

Comment 2 Joseph Marques 2010-06-24 12:22:58 UTC
I've duplicated this bug in a dev environment.  Working on it now.

Comment 3 Sudhir D 2010-06-24 12:39:12 UTC
Well, I did check the server log, agent log but did not find anything when I reproduced the issue.. so had to file without any log snippet.

Comment 4 Sudhir D 2010-06-24 12:46:18 UTC
Well, I did check the server log, agent log but did not find anything when I reproduced the issue.. so had to file without any log snippet.

Comment 5 Joseph Marques 2010-06-24 12:53:03 UTC
Sudhir, fair point.  In that case, the *lack of* any stack trace in the server log is an important piece of information to note as.  Without explicitly stating that, I can't tell whether 1) it didn't generate a stack trace in the log file for you, or 2) you forgot to attach it.  In any event, I've isolated the issue and am working on a patch for this bug right now.

Comment 6 Joseph Marques 2010-06-24 20:25:22 UTC
commit 50294ebe870e04f3673cf075dbf0420dcd083d62
Author: Joseph Marques <joseph>
Date:   Thu Jun 24 16:16:49 2010 -0400

    BZ-607548: prevent NPE when use operation-based alert notifications

Comment 7 Sudhir D 2010-06-29 07:08:13 UTC
Verified this on jon-server-2.4.0.GA_QA Build# 42. I don't see the NPE anymore.

Comment 8 Corey Welton 2010-08-12 16:46:54 UTC
Mass-closure of verified bugs against JON.


Note You need to log in before you can comment on or make changes to this bug.