Bug 1099621

Summary:	Serialization Exception when scheduling operation for resource with an alert definition
Product:	[Other] RHQ Project	Reporter:	Jay Shaughnessy <jshaughn>
Component:	Operations	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	hrupp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-21 15:07:16 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:

Description Jay Shaughnessy 2014-05-20 18:52:25 UTC

How reproducible: Always

Steps to Reproduce:
1. Create an alert definition on a resource.
   - For example, a abs threshold condition on a platform metric
2. Schedule an operation on the same resource.
   - For example, View process list on the platform

Actual results: Server-Side error:

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/coregui]] (http-/0.0.0.0:7080-7) org.rhq.coregui.CoreGUI OperationGWTService: An IncompatibleRemoteServiceException was thrown while processing this call.: 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



Marking for 4.11 although I'm not sure yet whether it affects 4.11 but I think it might.  I'll correct later depending on what we find.

Comment 1 Jay Shaughnessy 2014-05-21 13:13:23 UTC

This may be a gwt 2.5.0 issue.  I rebuilt with gwt 2.4.0 and it things worked fine both in dev mode and in web mode.

The issue happens in 2.5.0 when the Resource being passed into scheduleResourceOperation has the previously created alert def hanging on it.  Which happens when you create the alert def and then schedule the op, in the same detail view.  

The workaround is to in some way refresh your detail view after the alert def creation and before the operation scheduling.

Comment 2 Jay Shaughnessy 2014-05-21 15:07:16 UTC

This was reported in a separate BZ under different conditions... closing as duplicate of Bug 1058318.

*** This bug has been marked as a duplicate of bug 1058318 ***