curforever opened a new pull request, #4401: URL: https://github.com/apache/logging-log4j2/pull/4401
`ThrowableAttributeConverter` loses a non-null message when restoring a throwable that has a public no-arg constructor but no `String` constructor and no cause. The fallback assigns `cause` (null in that branch) to `detailMessage`. Assign the parsed `message` instead. Add round-trip coverage for no-arg-only exceptions with a message, with a cause, and without a message; verify type, message, cause and stack trace. No database-format or public API changes. Validation on Windows / JDK 17.0.5 / the Maven 3.9.16 wrapper: - The identical 8-test converter suite has 1 failure on the original source (expected message, actual null); all 8 pass with the fix. - `./mvnw verify site -pl :log4j-jpa`: 60 passed, 0 default skips, no failures/errors, including the 8 converter tests. No test selector, additional skip flags or build-file changes in this verification. Local reactor dependencies were installed separately using the converter test selector. - Full `./mvnw verify site` was attempted but stops in `log4j-core-test`: 1 UTF-8 decoding error in `RollingAppenderCronOnStartupTest` and 8 timeouts in `TlsSocketAppenderTest`. Restoring the original production source reproduces the same 9 failing cases. Process-level UTF-8 configuration resolves the decoding error; 8 TLS timeouts remain. Later reactor modules were not reported as passing. Docker/Java 8 and the wider CI matrix were not run locally. AI-generated with OpenAI Codex; the reported tests and checks were executed locally. -- 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]
