2021-01-26 22:26:21,737 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:100 – The application detected that a custom logging file exists: F:\Tomcat\conf\logging.properties. The application was unable to suppress various debugging messages.
2021-01-26 22:26:21,745 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:101 – In order to manually suppress Jersey debugging messages, the following logger levels must be adjusted to ”WARNING”: com.sun.jersey.api.core.PackagesResourceConfig, com.sun.jersey.server.impl.application.DeferredResourceConfig, and com.sun.jersey.server.impl.application.WebApplicationImpl
2021-01-26 22:26:21,746 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:102 – In order to manually suppress JSF debugging messages, the following logger level must be adjusted to ”SEVERE”: org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlRendererUtils
4 Comments
i added below logger in log4j.properties file but logs are not printing in logs file..
log4j.logger.sailpoint.demo.ad=debug
Pls see comment in another thread related to log4j
2021-01-26 22:26:21,737 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:100 – The application detected that a custom logging file exists: F:\Tomcat\conf\logging.properties. The application was unable to suppress various debugging messages.
2021-01-26 22:26:21,745 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:101 – In order to manually suppress Jersey debugging messages, the following logger levels must be adjusted to ”WARNING”: com.sun.jersey.api.core.PackagesResourceConfig, com.sun.jersey.server.impl.application.DeferredResourceConfig, and com.sun.jersey.server.impl.application.WebApplicationImpl
2021-01-26 22:26:21,746 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:102 – In order to manually suppress JSF debugging messages, the following logger level must be adjusted to ”SEVERE”: org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlRendererUtils
Hi, Probably you need to set log level (log4j.rootlogger) to debug or higher. Priority level is
OFF
FATAL
ERROR
WARN
INFO
DEBUG
TRACE
ALL
You have to edit sailpoint log4j properties which is in WEB-INF\classes I believe.
or you can set the logging level in code as well with something like this
Logger.getRootLogger().setLevel(Level.DEBUG);
or if you want to avoid adding imports:
org.apache.log4j.Logger.getRootLogger().setLevel(
org.apache.log4j.Level.DEBUG);
Note: this doesn’t work in log4j2 because setLevel has been removed from the API, and there doesn’t appear to be equivalent functionality