Bug 535565 – Tree chaching too aggressive

This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 535565 - (RHQ-2247) Tree chaching too aggressive

Summary:	Tree chaching too aggressive

Status:	CLOSED NOTABUG

Aliases:	RHQ-2247

Product:	RHQ Project
Classification:	Other
Component:	Core UI (Show other bugs)
Sub Component:
Version:	1.2
Hardware:	All All

Priority	low Severity medium (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	RHQ Project Maintainer
QA Contact:
Docs Contact:

URL:	http://jira.rhq-project.org/browse/RH...
Whiteboard:
Keywords:	SubBug

Depends On:
Blocks:	rhq4
	Show dependency tree / graph

Reported:	2009-07-20 04:41 EDT by Heiko W. Rupp
Modified:	2011-02-11 17:24 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-02-11 17:24:52 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Heiko W. Rupp 2009-07-20 04:41:00 EDT

I added a new war file through "create new ... war" successfully. After creation it did not show up in the tree - even when I was opening/closing the folder the resources show in.
The war only showed up when I went to the parents inventory, selected the war file and clicked on its link to the summary tab.

Comment 1 Red Hat Bugzilla 2009-11-10 16:00:45 EST

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2247

Comment 2 wes hayutin 2010-02-16 11:56:02 EST

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 12:01:12 EST

making sure we're not missing any bugs in rhq_triage

Comment 4 John Mazzitelli 2011-02-11 17:24:52 EST

this is a jsf bug, we use gwt now

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