Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1088565

Summary:

Resource Alert Save Fails Intermittently

Product:

[JBoss] JBoss Operations Network

Reporter:

Matt Mahoney <mmahoney>

Component:

Assignee:

RHQ Project Maintainer <rhq-maint>

Status:

CLOSED NOTABUG

QA Contact:

Mike Foley <mfoley>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

JON 3.2

CC:

jshaughn, mmahoney

Target Milestone:

---

Target Release:

JON 3.3.0

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-09-03 17:26:30 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Server.log	none

Description Matt Mahoney 2014-04-16 18:32:31 UTC

Description of problem:
When creating and saving a Resource Alert, the following error intermittently occurs, and the new Alert is not created:

	"Alert definition creation failed"

Version-Release number of selected component (if applicable):
4.11.0-SNAPSHOT

How reproducible:
Intermittently (perhaps once every 3 new Alerts)

Steps to Reproduce:
1. Navigate to a resource, such as an Agent.
2. Create a new Alert. Parameters used during testing were:
  Name: Agent - Goes Up
  Condition Type: Availability Change
  Availability: Goes Up


Actual results:
Dashboard error message "Alert definition creation failed", and new Alert is not saved.

Expected results:
New Alerts should be saved successfully.

Additional info:

Comment 1 Matt Mahoney 2014-04-16 19:29:16 UTC

Created attachment 886972 [details]
Server.log

Comment 2 Matt Mahoney 2014-04-16 19:29:49 UTC

Message :	
Alert definition creation failed
Severity :	
Error
	
Time :	
Wednesday, April 16, 2014 2:14:38 PM UTC-4
Root Cause :	
Attempt to deserialize an object of type class org.rhq.core.domain.alert.AlertCondition when an object of type class org.rhq.core.domain.alert.AlertDefinition is expected
Detail :	

com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:Attempt to deserialize an object of type class org.rhq.core.domain.alert.AlertCondition when an object of type class org.rhq.core.domain.alert.AlertDefinition is expected
--- STACK TRACE FOLLOWS ---
Attempt to deserialize an object of type class org.rhq.core.domain.alert.AlertCondition when an object of type class org.rhq.core.domain.alert.AlertDefinition is expected
   at Unknown.Throwable_1(Unknown Source)
   at Unknown.Exception_1(Unknown Source)
   at Unknown.RuntimeException_1(Unknown Source)
   at Unknown.IncompatibleRemoteServiceException_0(Unknown Source)
   at Unknown.instantiate_4(Unknown Source)
   at Unknown.$instantiate_0(Unknown Source)
   at Unknown.$instantiate(Unknown Source)
   at Unknown.$readObject(Unknown Source)
   at Unknown.$onResponseReceived(Unknown Source)
   at Unknown.onResponseReceived_4(Unknown Source)
   at Unknown.$fireOnResponseReceived(Unknown Source)
   at Unknown.onReadyStateChange_0(Unknown Source)
   at Unknown.this$static.onreadystatechange<(Unknown Source)
   at Unknown.apply(Unknown Source)
   at Unknown.entry0(Unknown Source)
   at Unknown.anonymous(Unknown Source)
   at Unknown.anonymous(Unknown Source)

Comment 3 Jay Shaughnessy 2014-07-03 17:37:43 UTC

I see that error in the log as well.  This would indicate some sort of bad build or out of date browser client.  Can you validate your environment?  I don't think this is a real issue. Asking Matt to see if he thinks this is still real...

Comment 4 Matt Mahoney 2014-09-03 17:26:30 UTC

Not reproducible in JON 3.3 ER01. Closing.