Bug 1103375 - Viewing operation details for operations with no results throws uncaught exception in GUI
Summary: Viewing operation details for operations with no results throws uncaught exce...
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI, Operations
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: GA
: RHQ 4.12
Assignee: Jay Shaughnessy
QA Contact: Mike Foley
Depends On:
Blocks: 1105743
TreeView+ depends on / blocked
Reported: 2014-05-30 21:23 UTC by Jay Shaughnessy
Modified: 2014-12-15 11:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-12-15 11:36:13 UTC

Attachments (Terms of Use)

Description Jay Shaughnessy 2014-05-30 21:23:36 UTC
1. Bring down agent
2. Schedule an op like "get all plugin info" for said agent
3. wait for op to fail because it can't connect to agent
4. view op details

This generates an exception.

Comment 1 Jay Shaughnessy 2014-05-30 21:33:22 UTC
I'm fairly sure this worked in the past, but I can't figure out when this behavior started.  It seems a while back, maybe 4.9 or earlier because I see this in JON 3.2.x branch as well.

Anyway, according to the data model it is supported that an operation, whether successful or not, can return null results.  This should be handled at all relevant points.

Committing fixes to GUI where I know we didn't handle null results, one in the op history detail view, and one in the agent topology detail view.  Also found a place in the server code where we potentially could lose history information.

commit ed8a2c4ce29920559febbd23129db6d9afa77d99
Author: Jay Shaughnessy <jshaughn@redhat.com>
Date:   Fri May 30 17:29:28 2014 -0400

    - Handled cases where null results are returned from an operation execution.
    - Fixed one op history update path where [results] data could be lost.

Comment 2 Heiko W. Rupp 2014-12-15 11:36:13 UTC
Bulk close of items fixed in RHQ 4.12

If you think this is not solved, then please open a *new* BZ and link to this one.

Note You need to log in before you can comment on or make changes to this bug.