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.