Bug 569546 - NPE occurs deterministically when adding a Measurement Baseline condition to a new Alert using the new Alert UI
Summary: NPE occurs deterministically when adding a Measurement Baseline condition to ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Alerts
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Justin Harris
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: rhq_sprint06
TreeView+ depends on / blocked
 
Reported: 2010-03-01 17:04 UTC by Steve Salevan
Modified: 2015-01-04 23:41 UTC (History)
3 users (show)

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


Attachments (Terms of Use)
printout of JBoss Seam debug page (98.26 KB, application/pdf)
2010-03-01 17:04 UTC, Steve Salevan
no flags Details

Description Steve Salevan 2010-03-01 17:04:12 UTC
Created attachment 397127 [details]
printout of JBoss Seam debug page

Description of problem:
If a user creates an alert and adds a Measurement Baseline condition with the following arguments:

Active Thread Count > 101 (max value)

they will deterministically reach a JBoss Seam Debug page, which reports the following exception:

Exception during request processing:
Caused by javax.servlet.ServletException with message: "#{alertConditionsUIBean.updateCondition}: java.lang.NullPointerException" 

Caused by javax.faces.el.EvaluationException with message: "java.lang.NullPointerException"

A PDF containing a full printout of this debug page has been attached, and one can reach the page itself at:

http://10.16.120.52:7080/debug.xhtml?conversationId=2224

Version-Release number of selected component (if applicable):
RHQ-alertPlugin branch, 2/23 git checkout

How reproducible:
Deterministic

Steps to Reproduce:
1. Create an alert, adding a Measurement Baseline condition such as the one above
  
Actual results:
As above

Expected results:
Condition added successfully

Additional info:

Comment 1 Justin Harris 2010-03-05 18:21:00 UTC
I'm having trouble reproducing this one as well.  Can you make sure that this is still happening with the current master build?

Comment 2 Steve Salevan 2010-03-09 18:05:42 UTC
This issue no longer presents in a 5/9 master branch git pull build.  Moving to VERIFIED.

Comment 3 wes hayutin 2010-03-10 14:19:45 UTC
moving verified bugs to rhq_sprint06, and removing from rhq_chainsaw

Comment 8 Corey Welton 2010-08-12 16:58:06 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.