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
> > 6076
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> Er
+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:9
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 P
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:
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
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
(includin
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
(includin
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
