Description
We are observing that log messages are getting truncated when logged using Log4j, particularly when using the following configuration:
This impacts critical logs such as log.fatal(message, throwable) where the complete message or stack trace is not fully printed. This is particularly noticeable for fatal and error logs where the message size is significantly large.
Configuration
Version: 2.25.3
Operating system: macOS 15.6
JDK: OpenJDK 17.0.12
Reproduction
- Configure Log4j with:
-
Log a message with a large string or exception:
-
log.fatal("Large message...", throwable);
Check the output logs.
Description
We are observing that log messages are getting truncated when logged using Log4j, particularly when using the following configuration:
This impacts critical logs such as log.fatal(message, throwable) where the complete message or stack trace is not fully printed. This is particularly noticeable for fatal and error logs where the message size is significantly large.
Configuration
Version: 2.25.3
Operating system: macOS 15.6
JDK: OpenJDK 17.0.12
Reproduction
Log a message with a large string or exception:
log.fatal("Large message...", throwable);
Check the output logs.