Olog client spams CONFIG logs when created

[arnaudf-iter]

When creating an Olog client, we are spammed by CONFIG logs from com.sun.jersey libraries:

com.sun.jersey.core.spi.component
com.sun.jersey.spi.service.ServiceFinder

We tried to use some trick to avoid them but the client is loaded before application start in org.csstudio.utility.olog.OlogClientFromPreferences

We should have a preference to enable/disable this logs.
Here is the trick that we used in our products:

private static final String[] VERBOSE_PACKAGES = new String[] {
            "com.sun.jersey.core.spi.component",
            "com.sun.jersey.spi.service.ServiceFinder" };
[...]
Level verboseLogLevel = Preferences.getVerboseLogLevel();
for (String verbosePackage : VERBOSE_PACKAGES) {
  Logger logger = Logger.getLogger(verbosePackage);
  logger.setLevel(verboseLogLevel);
  for (Handler handler : logger.getHandlers())
    handler.setLevel(verboseLogLevel);
}

[shroffk]

With the current default logging configuration, on startup the jersey libraries print a lot of CONFIG log to the console output. This tends to hide useful startup logs.

Solution 1.

Use a correctly configured logging.properties file and reference it via the following jvm argument -Djava.util.logging.config.file=....path to logging.properties.

Here is the example logging.properties file which only logs INFO level messages from jersey.

# Properties file which configures the operation of the JDK 
# logging facility.

# The system will look for this config file, first using 
# a System property specified at startup: 
# 
# >java -Djava.util.logging.config.file=myLoggingConfigFilePath 
# 
# If this property is not specified, then the config file is 
# retrieved from its default location at: 
# 
# JDK_HOME/jre/lib/logging.properties

# Global logging properties. 
# ------------------------------------------ 
# The set of handlers to be loaded upon startup. 
# Comma-separated list of class names. 
# (? LogManager docs say no comma here, but JDK example has comma.) 
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler

# Default global logging level. 
# Loggers and Handlers may override this level 
.level=INFO

# Loggers 
# ------------------------------------------ 
# Loggers are usually attached to packages. 
# Here, the level for each package is specified. 
# The global level is used by default, so levels 
# specified here simply act as an override. 
com.sun.jersey.level=INFO

# Handlers 
# -----------------------------------------

# --- ConsoleHandler --- 
# Override of global logging level 
java.util.logging.ConsoleHandler.level=CONFIG 
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter

Solution 2.

This is the solution implemented by ITER, except I have moved the logger configuration into the platform,libs.jersey plugin. Since this is the plugin which provides the jersery packages, it seems to be the appropriate place to define the logging preference for these packages.