ramanathan1504 commented on issue #2073:
URL:
https://github.com/apache/logging-log4j2/issues/2073#issuecomment-4575380821
## 1) Original report characteristics:
- RollingFileAppender created repeatedly
- Cron schedule: `0/1 0/1 * 1/1 * ? *` (every second)
- Random NPE path includes:
- `ConfigurationScheduler$CronRunnable.toString(...)`
- `ConfigurationScheduler.toString(...)`
- `CronTriggeringPolicy.initialize(...)`
Goal of this run:
- Execute a standalone stress harness against two Log4j versions (`2.17.2`,
`2.26.0`) using explicit runtime classpaths.
- Detect whether the Issue #2073 style NPE reproduces.
## 2) Harness Used
Important harness behavior:
- Uses cron schedule `0/1 0/1 * 1/1 * ? *`
- Creates many `RollingFileAppender` instances under concurrent workers
- Starts/stops appenders in loops
- Captures first failure, if any
- Classifies failure as `reproduced` only when stack trace matches Issue
#2073 signature
## 3) Inputs
- Stress inputs:
- `iterationsPerWorker=300`
- `workers=4`
- total planned attempts per run: `1200`
Compared Log4j versions (runtime classpath selection):
- `org.apache.logging.log4j:log4j-core:2.17.2`
- `org.apache.logging.log4j:log4j-api:2.17.2`
- `org.apache.logging.log4j:log4j-core:2.26.0`
- `org.apache.logging.log4j:log4j-api:2.26.0`
## 4) Raw Outputs
### 5.1 Log4j 2.17.2 (`/tmp/issue2073-2.17.2.out`)
```text
issue=2073
log4jVersion=2.17.2
schedule=0/1 0/1 * 1/1 * ? *
workers=4
iterationsPerWorker=300
attempts=1200
successfulBuilds=1200
durationMs=25376
logDir=/Users/ramanathan/apache/log4j2-workout/logs/issue-2073-standalone
status=not-reproduced
```
### 5.2 Log4j 2.26.0 (`/tmp/issue2073-2.26.0.out`)
```text
issue=2073
log4jVersion=2.26.0
schedule=0/1 0/1 * 1/1 * ? *
workers=4
iterationsPerWorker=300
attempts=1200
successfulBuilds=1200
durationMs=33524
logDir=/Users/ramanathan/apache/log4j2-workout/logs/issue-2073-standalone
status=not-reproduced
```
### 5.3 Exception Scan Result
- `grep` found no `NullPointerException` and no `Exception` strings in
either output file.
## 6) Result Summary
- Issue #2073 NPE was **not reproduced** in this test window.
- Both versions completed all planned attempts successfully:
- `2.17.2`: `1200/1200`
- `2.26.0`: `1200/1200`
| Metric | 2.17.2 | 2.26.0 |
|-------------------|---------------:|---------------:|
| Attempts | 1200 | 1200 |
| Successful builds | 1200 | 1200 |
| Failures | 0 | 0 |
| Status | not-reproduced | not-reproduced |
| Duration (ms) | 25376 | 33524 |
## 6) Notes and Limits
- This run used macOS + JBR 17 in the current workspace.
- Original incident mentions Ubuntu 22.04 + Temurin 11.
- The run is high-frequency and concurrent, but bounded (`300 x 4`) rather
than an infinite loop.
- Since the issue is random by nature, non-reproduction in one window does
not prove impossibility.
If needed, mirror original environment exactly (Ubuntu 22.04 + Temurin 11)
and repeat the same matrix.
--
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]
