-
Bug
-
Resolution: Done
-
Major
-
8.0 Update 3
-
None
-
False
-
None
-
False
-
-
-
-
-
-
Workaround Exists
-
-
- Configure DEBUG logging
- Start server
- Check server log
-
-
If server has set DEBUG logging enabled e.g. 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>
There's hundreds MB of extra debug logs from
DEBUG [com.networknt.schema.PropertiesValidator] (ServerService Thread Pool -- 1) validate( {"schemaVersion":"1.0.0","streams":[{"groupId":"com.amazonaws","artifactId":"aws-java-sdk-core",...
A single startup with the mentioned configuration produces a 415MB log file.
This is a related issue to JBEAP-26023 in that it has the same root cause.
The difference is that the same logging is now also triggered by the changes from JBEAP-26315.
That makes the situation worse, because this happens on every startup/restart as long as debug logging is enabled.
In the case of Insights also being active, this results in a 830MB log file just from a single server startup alone.
- is incorporated by
-
JBEAP-27543 (8.0.z) Upgrade WildFly Core from 21.0.10.Final-redhat-00001 to 21.0.11.Final-redhat-00001 in EAP 8.0 Update 4
-
- Closed
-
- relates to
-
-
- Closed
-
-
WFCORE-6600 Limit logging level of com.networknt.schema
-
- Resolved
-
