Bug 569559

Summary: If a user creates an alert, adding a condition with invalid input, the invalid input will be accepted
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:54:49 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
JBoss Seam Debug page none

Description Steve Salevan 2010-03-01 17:33:49 UTC
Description of problem:
If a user creates an Alert for a platform, adding the following Measurement Threshold condition to it:

Active Thread Count > 1nonNum&^*^#1

the input will be accepted and the following error message will appear on the Alert creation page:

/rhq/resource/alert/listConditions.xhtml @276,132 value="#{alertConditionsUIBean.threshold}": Error writing 'threshold' on type org.rhq.enterprise.gui.alert.AlertConditionsUIBean_$$_javassist_14

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

How reproducible:
Always

Steps to Reproduce:
1. Create an alert with invalid input similar to that reported
  
Actual results:
Similar to above

Expected results:
Input rejected

Additional info:

Comment 1 Steve Salevan 2010-03-01 17:44:11 UTC
Created attachment 397137 [details]
JBoss Seam Debug page

It appears that, if a user creates a Measurement Baseline alert as well, with:

Active Thread Count > -99 of max value

they will receive a traceback similar to that attached.

Comment 2 Justin Harris 2010-03-05 15:41:54 UTC
Current build of master results in proper error messages displayed for both cases.  This is a 'Works for me'.   Can you verify Steve?

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

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

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