Bug 580883

Summary: Alert: 'NEW DEFINITION' is failed with java.lang.IllegalArgumentException: can't parse argument number product.shortName
Product: [Other] RHQ Project Reporter: Rajan Timaniya <rtimaniy>
Component: AlertsAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: low    
Version: 3.0.0   
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:44:17 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: 565628    
Attachments:
Description Flags
screenshot
none
screenshot for exception none

Description Rajan Timaniya 2010-04-09 10:46:52 UTC
Created attachment 405518 [details]
screenshot

Description of problem:
Alert 'NEW DEFINITION' is not working. It gives the error: 'java.lang.IllegalArgumentException: can't parse argument number product.shortName at'

Version-Release number of selected component (if applicable):
Jon Build #81 Revision: 10600

How reproducible:
Always

Steps to Reproduce:
1) Log into RHQ Server
2) Select 'Alert' tab of any resource
3) Click on 'NEW DEFINITION'
  
Actual results:
Alert 'NEW DEFINITION' is not working. It gives the error: 'java.lang.IllegalArgumentException: can't parse argument number product.shortName at'.

Expected results:
Alert 'NEW DEFINITION' should works without any error.

Additional info:
java.lang.IllegalArgumentException: can't parse argument number product.shortName at java.text.MessageFormat.makeFormat(MessageFormat.java:1339) at java.text.MessageFormat.applyPattern(MessageFormat.java:458) at org.apache.taglibs.standard.tag.common.fmt.MessageSupport.doEndTag(MessageSupport.java:190) at org.apache.jsp.portal.MainLayout_jsp._jspx_meth_fmt_005fmessage_005f0(MainLayout_jsp.java:244) at org.apache.jsp.portal.MainLayout_jsp._jspx_meth_html_005fhtml_005f0(MainLayout_jsp.java:139) at org.apache.jsp.portal.MainLayout_jsp._jspService(MainLayout_jsp.java:82) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336) at 
...

Comment 1 Rajan Timaniya 2010-04-09 13:59:26 UTC
Created attachment 405555 [details]
screenshot for exception

Comment 2 Rajan Timaniya 2010-04-15 11:38:39 UTC
Verified on JON build #88 - Revision: 10607

Alert 'NEW DEFINITION' functionality is working fine.

Comment 3 Charles Crouch 2010-04-27 17:52:34 UTC
Rajan, please update the status appropriately. Thanks

Comment 4 Rajan Timaniya 2010-04-28 06:09:17 UTC
Verified on JON build #112 - Revision: 10615

Alert 'NEW DEFINITION' functionality is working fine.

Comment 5 Corey Welton 2010-08-12 16:44:17 UTC
Mass-closure of verified bugs against JON.