-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
8.0.0.GA-CR1, 8.0.0.GA-CR2
-
None
-
False
-
None
-
False
-
-
-
-
-
-
Known Issue
-
-
If server has set DEBUG logging like:
<subsystem xmlns="urn:jboss:domain:logging:8.0"> ... <periodic-rotating-file-handler name="FILE" autoflush="true"> <level name="DEBUG"/> ... </periodic-rotating-file-handler> ... <root-logger> <level name="DEBUG"/> <handlers> <handler name="CONSOLE"/> <handler name="FILE"/> </handlers> </root-logger> .... </subsystem>
and Insights is enabled then during generating report there is excessive logging when generating Insights report. It generates ~500MB of DEBUG logs per report.
Additional notes - example of debug message (see junit-report.zip):
22:45:48,164 DEBUG [com.networknt.schema.PropertiesValidator] (ServerService Thread Pool -- 1) validate( {"schemaVersion":"1.0.0","streams":[{"groupId":"com.amazonaws","artifactId":"aws-java-sdk-core",...
Note this happens only with server with prospero module (json-schema-validator). It seems that generating Insights report triggers it:
$ grep -r com.networknt.schema grep: modules/system/layers/base/org/jboss/prospero/main/json-schema-validator-1.0.82.redhat-00004.jar: binary file matches bin/jboss-eap-installation-manager-logging.properties:loggers=org.wildfly.prospero,com.networknt.schema,org.eclipse.aether.internal.impl bin/jboss-eap-installation-manager-logging.properties:logger.com.networknt.schema.level=INFO bin/jboss-eap-installation-manager-logging.properties:logger.com.networknt.schema.handlers=FILE
Customer Impact: None when set logging on INFO level (which is default) In case that DEBUG logging and Insights are enabled, huge log files can be generated and potentially crash server on out of disk space.
- is related to
-
WFCORE-6600 Limit logging level of com.networknt.schema
-
- Resolved
-
