Bug 535697 (RHQ-2366)

Summary: Excessive Configuration Changes Detected on java.util.Logging resources
Product: [Other] RHQ Project Reporter: Greg Hinkle <ghinkle>
Component: No ComponentAssignee: Greg Hinkle <ghinkle>
Status: CLOSED NEXTRELEASE QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecified   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-2366
Whiteboard:
Fixed In Version: 1.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Greg Hinkle 2009-08-19 04:19:00 UTC 
Logging resources under the JVM resource type have configuration support that display the currently defined logging categories. The problem is that as more and more code runs in a given JVM it'll initialize more categories. This interacts with the configuration check subsystem to cause an excessive # of changes to be detected. This can have a serious performance impact in very large environments.

To avoid this set of problems we'll have a plugin configuration for the Logging resource type that allows you to enable it configuration facet. It will default to false thus avoiding these detected config changes.
Comment 1 Corey Welton 2009-08-31 13:51:13 UTC 
Not sure what we're supposed to be looking at in the UI here to confirm this new config option.
Comment 2 Charles Crouch 2009-08-31 15:09:55 UTC 
It will be on the Logging service beneath a JVM Server. You'll want to go to the Connection subtab of the Inventory tab in the UI
Comment 3 Corey Welton 2009-09-09 18:31:39 UTC 
QA Verified.
Comment 4 Red Hat Bugzilla 2009-11-10 21:03:00 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2366