Bug 569546

Summary: NPE occurs deterministically when adding a Measurement Baseline condition to a new Alert using the new Alert UI
Product: [Other] RHQ Project Reporter: Steve Salevan <ssalevan>
Component: AlertsAssignee: Justin Harris <jharris>
Status: CLOSED CURRENTRELEASE QA Contact: Chandrasekar Kannan <ckannan>
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: benl, ckannan, jkeck
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:58:06 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: 565617    
Attachments:
Description Flags
printout of JBoss Seam debug page none

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.