The XStreamPersister logs statements such as
"Loaded store 'nyc', enabled"
"Loaded feature type 'states', enabled"
These statements are duplicated in the GeoServerLoader,but without enabled/disabled info. Also, coverages are there incorrectly logged as feature types.
The problem is that the XStreamPersister isn't only used by GeoServerLoader, but also for example by the hazelcast-jdbcconfig cache.
If you have clustered jdbc configuration with a very large catalog, every GetCapabilities request will cause massive log output (for each feature type and store), suggesting that these objects are being "loaded" (which is incorrect, they are merely queried). I am dealing with a setup that uses a healthcheck that calls GetCapabilities on a regular interval. The logs are being flooded with this stuff, making them unusable and causing perforamnce overhead.
My suggestion is to
remove these log statements from the XStreamPersister
add enabled/disabled info to the ones in GeoServerLoader
fix the resource logging in GeoServerLoader, to take into account coverages