Bug 535815 (RHQ-2472)

Summary: Stack trace is empty upon clicking a "Failed" resource config history change
Product: [Other] RHQ Project Reporter: John Sefler <jsefler>
Component: PluginsAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: low    
Version: 1.3CC: cwelton, jshaughn, whayutin
Target Milestone: ---Keywords: SubBug
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-2472
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-12 19:14: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: 625146    
Attachments:
Description Flags
Screenshot-JON - JMQ JMS Queue 'testAutoQueue1255730763109 JMS Queue' - View Configuration History - Mozilla Firefox.png none

Description John Sefler 2009-10-20 16:24:00 UTC 
We created a JMS Topic within the inventory of a JBoss AS resource
We opened the new config file on disk (somewhere under the deploy dir) using vi (leave it open).
From the JON GUI, edit and save a change to the JMS Topic ->
  This results in a Failed entry in the config "History" for this resource.
  Click on the "Failed" link and a stack trace is displayed.
  The defect is that the stack trace is empty.  See attached screenshot.
Comment 1 Red Hat Bugzilla 2009-11-10 21:05:06 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2472
Imported an attachment (id=368805)
Comment 2 wes hayutin 2010-02-16 16:52:27 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 3 wes hayutin 2010-02-16 16:58:13 UTC 
making sure we're not missing any bugs in rhq_triage