Bug 534962 (RHQ-1707) - Issues with CacheConsistencyManagerBean
Summary: Issues with CacheConsistencyManagerBean
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: RHQ-1707
Product: RHQ Project
Classification: Other
Component: Alerts
Version: 1.2
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks: rhq-perf
TreeView+ depends on / blocked
 
Reported: 2009-03-03 04:50 UTC by Charles Crouch
Modified: 2015-02-01 23:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-05 15:18:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Charles Crouch 2009-03-03 04:50:00 UTC
Saw this in the server log 

[org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] jon03.qa.atl2.redhat.com took [378399]ms to reload cache for 250 agents

a) Over 6mins seems a bit long, not sure if that is to be expected.
b) I dont have 250agents in the inventory, I have 218 in inventory and 32 uncommitted in the autodiscovery portlet.

Comment 1 Joseph Marques 2009-03-22 15:33:19 UTC
charles, did you only see this once, or is this consistent?  the cache shouldn't take anywhere near that long to load, so my first guess would be that your database was unhealthy in some other way and/or was busy processing some sort sort of data.  if this happens, you should turn on debug logging for the alerts-related SLSBs (this is already commented our in the server's log4j config file).

Comment 2 Red Hat Bugzilla 2009-11-10 20:38:48 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1707


Comment 3 Charles Crouch 2010-08-05 16:40:40 UTC
Need to test in the perf env to see if this is still a problem


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