Bug 562816
Summary: | Alert Enable process via Alert Page displays JAVA Exception | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | spandey |
Component: | Plugins | Assignee: | Joseph Marques <jmarques> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Welton <cwelton> |
Severity: | medium | Docs Contact: | |
Priority: | urgent | ||
Version: | 1.4.0.B01 | CC: | cwelton, kbanerje, sdharane, smohan, spandey, whayutin |
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:10 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: | 547833, 565632, 577217 |
Description
spandey
2010-02-08 13:27:24 UTC
mass move to rhq_chainsaw tracker bug This bug has now been triaged by Chainsaw on 2/18. The expectation is the bug to be addressed by the end of sprint06 roughly 3/10/10. In commit: c06cf9c470abf7d8c1bfff7b9969ce68de607105 fails_qa due to bugzilla 571888 the active toggle changes in the alert definition page, however when you go back to the resource alert list the setting has not changed. Joseph, can you take a look at this and see if its still a problem using any of the JON notifier plugins updated by ccrouch "confirmed - editing alert defns is broken." commit d3cc735b22ba4548e5eef68b1dae73bf51335649 fix for stack trace when trying to edit general properties or conditions for an alert definition tested on JON#116 Revision 10615 steps: 1)Create an alert for a given resource. 2)Used the condition used memory>0.1B. 2)Disable the newly created alert at "alert definition page". 3)Open the newly created alert. 4)Go to the alert notification section select the option select direct-email set OK. 5)Enter the receiver's email,click save. 6)Go to the alert properties button and re enable the alert and click on save. Observation there is a java lang number format execption. the error window and stack trace is pasted below. java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:470) at java.lang.Integer.(Integer.java:660) at org.rhq.enterprise.gui.legacy.action.resource.common.monitor.alerts.ReenableAlertDefinitionAction.execute(ReenableAlertDefinitionAction.java:58) at org.rhq.enterprise.gui.legacy.action.BaseRequestProcessor.processActionPerform(BaseRequestProcessor.java:46) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.rhq.enterprise.gui.legacy.WebUserTrackingFilter.doFilter(WebUserTrackingFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.rhq.enterprise.gui.legacy.AuthenticationFilter.doFilter(AuthenticationFilter.java:129) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.rhq.helpers.rtfilter.filter.RtFilter.doFilter(RtFilter.java:124) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) java.lang.NumberFormatException: For input string: "" The page requested cannot be displayed due to some error. You can view the stack trace, return to the previous page, Dashboard, or Browse Resources page. Need to see if the steps outlined in comment9 still cause problems Could not reproduce the exception. Here is everything I tried: 1) created resource-level, metric-based, initially disabled, alert definition 2) enabled / disabled it from list alert definition view 3) enabled / disabled it from edit properties 4) triggered a condition to make this alert fire at least once 5) repeated steps 2 & 3 6) edited condition set, used operation-based condition 7) repeated steps 2 through 5 8) repeated steps 1-7 for an alert template, making sure that updates at the template-level trickled down to the resource-level 9) repeated steps 1-7 for a group alert definition, making sure that updates at the group-level trickled down to the resource-level finally... 10) disabled all alert definitions created 11) visited details view for the alert created from the resource-level alert definition, clicked "re-enabled alert definition" link in the alert properties section 12) repeated step 11 for an alert created from the alert template 13) repeated step 11 for an alert created from the group alert definition Verified that no exception occurs in any of these scenarios and that the state of the alert-related objects get properly updated as expected. Agree with comment #12 -- I tried a bunch of different ways, using the steps outlined in comment #9 and was not able to repro the exception. Will close, we can reopen later if necessary. Mass-closure of verified bugs against JON. |