[VOTE] Release Apache Log4j `2.25.1` (RC1)
This is a vote to release the Apache Log4j `2.25.1`. Website: https://logging.staged.apache.org/log4j/2.25.1/index.html GitHub: https://github.com/apache/logging-log4j2 Commit: bda63362cf405449ff4edc2e4d92353be65c4d4e Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.25.1 Nexus: https://repository.apache.org:443/content/repositories/orgapachelogging-1320 Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 Review kit: https://logging.apache.org/logging-parent/release-review-instructions.html[*] Please download, test, and cast your votes on this mailing list. You can optionally also cast your vote in the ATR system[**]. [ ] +1, release the artifacts [ ] -1, don't release, because... This vote is open for 72 hours and will pass unless getting a net negative vote count. All votes are welcome and we encourage everyone to test the release, but only the Logging Services PMC votes are officially counted. At least 3 +1 votes and more positive than negative votes are required. [*] As with the 2.25.0 release, the aggregate SBOM for the log4j-bom artifact in version 2.25.1 is not fully reproducible. Two variants may be generated that differ only in the ordering of the `jspecify` dependency. This issue is known and tracked under GitHub issue #3804: https://github.com/apache/logging-log4j2/issues/3804 To avoid false negatives during verification, reviewers are asked to ignore this specific difference by appending the following parameter to the build command in the release review instructions: -Dbuildinfo.ignore="*/log4j-bom-2.25.1-cyclonedx.xml" [**] Please note that the Apache Trusted Release (ATR) tool is currently in alpha, and votes cast through ATR are not officially counted in the release process. However, Apache committers are encouraged to try it out and provide feedback using the following URL: https://release-test.apache.org/vote/logging-log4j/2.25.1 == Release Notes This patch release addresses a dozen bugs in version `2.25.0`, in particular: * Resolves a concurrency issue in the new unified datetime formatter. * Fixes build failures affecting Gradle users. * Restores backward compatibility with Spring Boot’s common logging configuration. * Improves handling of edge cases in GraalVM support. The complete changelog of the `2.25.1` release can be found on the staged website at: https://logging.staged.apache.org/log4j/2.25.1/release-notes.html#release-notes-2-25-1
Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)
+1 I tested the src zip file distribution: - GPG ok - SHA512 OK - mvn clean verify But it failed with Docker tests enabled: mvn clean verify -Pdocker -D'docker.showLogs=true' [ERROR] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Timeout after 60764 ms while waiting on tcp port '[/172.19.0.2:9200]' [ERROR] DOCKER> Error occurred during container startup, shutting down... [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Stop and removed container a095e36ff18f after 0 ms [ERROR] DOCKER> I/O Error [[elasticsearch:8.17.3] "elasticsearch": Timeout after 60764 ms while waiting on tcp port '[/172.19.0.2:9200]'] Using: openjdk version "17.0.15" 2025-04-15 OpenJDK Runtime Environment Homebrew (build 17.0.15+0) OpenJDK 64-Bit Server VM Homebrew (build 17.0.15+0, mixed mode, sharing) Apache Maven 3.9.10 (5f519b97e944483d878815739f519b2eade0a91d) Maven home: /opt/homebrew/Cellar/maven/3.9.10/libexec Java version: 17.0.15, vendor: Homebrew, runtime: /opt/homebrew/Cellar/openjdk@17/17.0.15/libexec/openjdk.jdk/Contents/Home Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "15.5", arch: "aarch64", family: "mac" Darwin .local 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041 arm64 Docker version 28.3.0, build 38b7060 Gary On Sat, Jul 5, 2025 at 5:08 PM Piotr P. Karwasz wrote: > > This is a vote to release the Apache Log4j `2.25.1`. > > Website: https://logging.staged.apache.org/log4j/2.25.1/index.html > GitHub: https://github.com/apache/logging-log4j2 > Commit: bda63362cf405449ff4edc2e4d92353be65c4d4e > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.25.1 > Nexus: > https://repository.apache.org:443/content/repositories/orgapachelogging-1320 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > Review kit: > https://logging.apache.org/logging-parent/release-review-instructions.html[*] > > Please download, test, and cast your votes on this mailing list. > You can optionally also cast your vote in the ATR system[**]. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... > > This vote is open for 72 hours and will pass unless getting a > net negative vote count. All votes are welcome and we encourage > everyone to test the release, but only the Logging Services PMC > votes are officially counted. At least 3 +1 votes and more > positive than negative votes are required. > > [*] As with the 2.25.0 release, the aggregate SBOM for the log4j-bom > artifact in version 2.25.1 is not fully reproducible. Two variants may > be generated that differ only in the ordering of the `jspecify` dependency. > > This issue is known and tracked under GitHub issue #3804: > > https://github.com/apache/logging-log4j2/issues/3804 > > To avoid false negatives during verification, reviewers are asked to > ignore this specific difference by appending the following parameter to > the build command in the release review instructions: > > -Dbuildinfo.ignore="*/log4j-bom-2.25.1-cyclonedx.xml" > > [**] Please note that the Apache Trusted Release (ATR) tool is currently > in alpha, and votes cast through ATR are not officially counted in the > release process. However, Apache committers are encouraged to try it out > and provide feedback using the following URL: > > https://release-test.apache.org/vote/logging-log4j/2.25.1 > > == Release Notes > > This patch release addresses a dozen bugs in version `2.25.0`, in > particular: > > * Resolves a concurrency issue in the new unified datetime formatter. > * Fixes build failures affecting Gradle users. > * Restores backward compatibility with Spring Boot’s common logging > configuration. > * Improves handling of edge cases in GraalVM support. > > The complete changelog of the `2.25.1` release can be found on the > staged website at: > > https://logging.staged.apache.org/log4j/2.25.1/release-notes.html#release-notes-2-25-1
Re: [D] Roadmap for `2.25.1` release [logging-log4j2]
GitHub user ppkarwasz added a comment to the discussion: Roadmap for `2.25.1`
release
The vote to release **Apache Log4j 2.25.1** has started and will remain open
for **72 hours**. We invite the community to test the release candidate to help
ensure a stable and reliable release.
## How to Participate
We encourage developers and users to verify the release artifacts **before**
they are published to Maven Central. Here’s how:
### Maven Users
Add the following to your project's `pom.xml`:
```xml
central
apache-logging-staging
https://repository.apache.org/content/repositories/orgapachelogging-1320
true
false
```
Then, update your Log4j dependencies to version `2.25.1`.
### Gradle Users
In your `build.gradle`, add the staging repository with proper filtering:
Groovy DSL
```groovy
repositories {
mavenCentral()
maven {
name = "apacheLoggingStaging"
url =
uri("https://repository.apache.org/content/repositories/orgapachelogging-1320";)
content {
includeGroup "org.apache.logging"
includeGroup "org.apache.logging.log4j"
}
}
}
```
Kotlin DSL
```kotlin
repositories {
mavenCentral()
maven {
name = "apacheLoggingStaging"
url =
uri("https://repository.apache.org/content/repositories/orgapachelogging-1320";)
content {
includeGroup("org.apache.logging")
includeGroup("org.apache.logging.log4j")
}
}
}
```
Then, update your Log4j dependencies to version `2.25.1`.
### Reporting Results
* Run your application and test it against the release candidate
* Report any successes or issues by replying to the official [vote
thread](https://lists.apache.org/thread/yhfgs50hlwmt9hvocr47ftzd3vowvb2m) on
the `dev@logging.apache.org` mailing list.
> [!NOTE]
> While only PMC members’ votes are binding, **community feedback is highly
> valued**—especially when it includes test results or bug reports.
Thank you for helping ensure a robust Log4j release!
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3766#discussioncomment-13671473
This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)
Hi Gary, On 5.07.2025 23:41, Gary Gregory wrote: > But it failed with Docker tests enabled: mvn clean verify -Pdocker > -D'docker.showLogs=true' > > [ERROR] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Timeout after > 60764 ms while waiting on tcp port '[/172.19.0.2:9200]' > [ERROR] DOCKER> Error occurred during container startup, shutting down... > > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Stop and > removed container a095e36ff18f after 0 ms > [ERROR] DOCKER> I/O Error [[elasticsearch:8.17.3] "elasticsearch": > Timeout after 60764 ms while waiting on tcp port '[/172.19.0.2:9200]'] Sorry about that. As we have seen in `2.25.0` this is a MacOS-specific Docker issue and we'll likely need help from someone familiar with Docker on Mac to investigate further. Are there any volunteers who could assist? I do have a Windows installation that I use for tasks that require it, so I can look into debugging the tests on that platform. Unfortunately, I can’t help with MacOS-specific issues. In the meantime, could you please open an issue in our tracker so we don’t lose track of this? Piotr
Re: [D] Exception causes are truncated while logging exceptions with line number limit [logging-log4j2]
GitHub user ZOUG added a comment to the discussion: Exception causes are
truncated while logging exceptions with line number limit
I was considering to move to `log4j2` from `logback`, whose default behavior
for `%ex{5}` is printing 5 lines of stack trace for **each exception level
(including the outermost exception and its causes)**. I wasn't aware of the
`%rEx` parameter before. So I tried `%rEx{5}` and it shows something like this.
```
java.lang.RuntimeException: Cause
... 74 more
Wrapped by: java.lang.RuntimeException: Nested exception
at com.example.LoggingTest.testLogger(LoggingTest.java:20)
~[test-classes/:?]
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
~[?:?]
```
The cause exception is shown -- which is helpful -- but its stack trace is
still not printed as expected.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3803#discussioncomment-13667884
This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
Re: [D] Exception causes are truncated while logging exceptions with line number limit [logging-log4j2]
GitHub user ZOUG edited a comment on the discussion: Exception causes are
truncated while logging exceptions with line number limit
I was considering to move to `log4j2` from `logback`, whose default behavior
for `%ex{5}` is printing 5 lines of stack trace for **each exception level
(including the outermost exception and its causes)**. I wasn't aware of the
`%rEx` parameter before. So I tried `%rEx{5}` and it shows something like this.
```
java.lang.RuntimeException: Cause
... 74 more
Wrapped by: java.lang.RuntimeException: Nested exception
at com.example.LoggingTest.testLogger(LoggingTest.java:20)
~[test-classes/:?]
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
~[?:?]
```
The cause exception is shown -- which is helpful -- but its stack trace is
still not printed as expected. Changing 5 to 10 doesn't change the output for
the cause exception.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3803#discussioncomment-13667884
This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
Re: [D] Exception causes are truncated while logging exceptions with line number limit [logging-log4j2]
GitHub user ZOUG edited a comment on the discussion: Exception causes are
truncated while logging exceptions with line number limit
I was considering to move to `log4j2` from `logback`, whose default behavior
for `%ex{5}` is printing 5 lines of stack trace for **each exception level
(including the outermost exception and its causes)**. I wasn't aware of the
`%rEx` parameter before. So I tried `%rEx{5}` and it shows something like this.
```
java.lang.RuntimeException: Cause
... 74 more
Wrapped by: java.lang.RuntimeException: Nested exception
at com.example.LoggingTest.testLogger(LoggingTest.java:20)
~[test-classes/:?]
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
~[?:?]
```
The cause exception is shown -- which is helpful -- but its stack trace is
still not printed as expected. Changing 5 to 10 doesn't affect the output of
the cause exception.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3803#discussioncomment-13667884
This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
Re: [D] Exception causes are truncated while logging exceptions with line number limit [logging-log4j2]
GitHub user ZOUG added a comment to the discussion: Exception causes are
truncated while logging exceptions with line number limit
You are right on this. There is indeed one related issue that is a potential
bug though. When I tried `%xEx{5}`, the depth level is ignored and the stack
trace is not truncated at all.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3803#discussioncomment-13667975
This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
Re: [VOTE] Release Apache Log4j `2.25.1` (RC1)
On Sat, Jul 5, 2025 at 5:54 PM Piotr P. Karwasz wrote: > > Hi Gary, > > On 5.07.2025 23:41, Gary Gregory wrote: > > But it failed with Docker tests enabled: mvn clean verify -Pdocker > > -D'docker.showLogs=true' > > > > [ERROR] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Timeout after > > 60764 ms while waiting on tcp port '[/172.19.0.2:9200]' > > [ERROR] DOCKER> Error occurred during container startup, shutting down... > > > > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Stop and > > removed container a095e36ff18f after 0 ms > > [ERROR] DOCKER> I/O Error [[elasticsearch:8.17.3] "elasticsearch": > > Timeout after 60764 ms while waiting on tcp port '[/172.19.0.2:9200]'] > > Sorry about that. As we have seen in `2.25.0` this is a MacOS-specific > Docker issue and we'll likely need help from someone familiar with > Docker on Mac to investigate further. Are there any volunteers who could > assist? > > I do have a Windows installation that I use for tasks that require it, > so I can look into debugging the tests on that platform. Unfortunately, > I can’t help with MacOS-specific issues. > > In the meantime, could you please open an issue in our tracker so we > don’t lose track of this? I created https://github.com/apache/logging-log4j2/issues/3805 Gary > > Piotr
