ramanathan1504 commented on issue #4088: URL: https://github.com/apache/logging-log4j2/issues/4088#issuecomment-4443130142
@veenaBOL # Reproducer Run Report Date: 2026-05-13 ## Scope This report was produced without modifying the original user files in the root folder: - `pom.xml` - `Repro.java` - `log4j2.xml` ## Folder setup Two separate folders were created from the same 3 user files: 1. `repro-original/` - direct copy, no dependency changes. 2. `repro-with-deps/` - same copy, then only `pom.xml` in this folder was updated. ## Change made only in `repro-with-deps/pom.xml` Added missing runtime dependencies required by the existing config: - `com.lmax:disruptor:3.4.4` (required by `AsyncLogger` / `AsyncRoot`) - `com.fasterxml.jackson.core:jackson-databind:2.18.2` (required by `JSONLayout`) Reference for async logging setup: - https://logging.apache.org/log4j/2.x/manual/async.html ## Run results | Check | `repro-original` | `repro-with-deps` | |---------------------|-----------------:|------------------:| | `stdout_lines` | 5 | 2 | | `stderr_lines` | 149 | 0 | | `has_json` | false | true | | `message_len` | 0 | 200000 | | `has_thrown` | false | true | | `stack_frames` | 0 | 1 | | `missing_jackson` | true | false | | `missing_disruptor` | true | false | ## Observed issue in original copy In `repro-original/`, Log4j configuration initialization reports missing classes for: - Jackson Databind (`FilterProvider`) - Disruptor (`com/lmax/disruptor/EventHandler`) Because of that, the intended `AsyncLogger + JSONLayout` path is not active in the original copied setup. ## Conclusion - The issue in the direct user-copy run is missing runtime dependencies for the configured logging pipeline. - After adding those dependencies in the second folder, the same code logs a full JSON event with full 200k message and throwable stack trace. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
