Bug 535815 (RHQ-2472) - Stack trace is empty upon clicking a "Failed" resource config history change
Summary: Stack trace is empty upon clicking a "Failed" resource config history change
Alias: RHQ-2472
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 1.3
Hardware: All
OS: All
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL: http://jira.rhq-project.org/browse/RH...
Depends On:
Blocks: jon30-bugs
TreeView+ depends on / blocked
Reported: 2009-10-20 16:24 UTC by John Sefler
Modified: 2014-05-12 19:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-05-12 19:14:10 UTC

Attachments (Terms of Use)
Screenshot-JON - JMQ JMS Queue 'testAutoQueue1255730763109 JMS Queue' - View Configuration History - Mozilla Firefox.png (144.80 KB, image/png)
2009-10-20 16:24 UTC, John Sefler
no flags Details

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.

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

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