+1 If I don't enable Docker, then the whole build passes, I can validate the src zip file with:
mvn clean verify FWIW, you can't just exclude "log4j-layout-template-json-test" with: mvn clean verify -Pdocker -D'docker.showLogs=true' -pl '!log4j-layout-template-json-test' because: [INFO] --- bnd-baseline:7.1.0:baseline (check-api-compat) @ log4j-osgi-test --- [INFO] [INFO] --------------< org.apache.logging.log4j:log4j-perf-test >-------------- [INFO] Building Apache Log4J Performance Tests 2.25.0 [34/40] [INFO] from log4j-perf-test/pom.xml [INFO] --------------------------------[ jar ]--------------------------------- Downloading from central: https://repo.maven.apache.org/maven2/org/apache/logging/log4j/log4j-layout-template-json-test/2.25.0/log4j-layout-template-json-test-2.25.0.pom [WARNING] The POM for org.apache.logging.log4j:log4j-layout-template-json-test:jar:2.25.0 is missing, no dependency information available Downloading from central: https://repo.maven.apache.org/maven2/org/apache/logging/log4j/log4j-layout-template-json-test/2.25.0/log4j-layout-template-json-test-2.25.0.jar [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for Apache Log4j BOM 2.25.0: [INFO] [INFO] Apache Log4j BOM ................................... SUCCESS [ 8.310 s] [INFO] Apache Log4j Parent ................................ SUCCESS [ 0.524 s] [INFO] Apache Log4j API Java 9 support .................... SUCCESS [ 3.451 s] [INFO] Apache Log4j API ................................... SUCCESS [ 8.557 s] [INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [ 2.198 s] [INFO] Apache Log4j Core .................................. SUCCESS [ 18.234 s] [INFO] Apache Log4j API Tests ............................. SUCCESS [ 10.939 s] [INFO] Apache Log4j Core Tests ............................ SUCCESS [01:13 min] [INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [ 12.593 s] [INFO] Apache Log4j App Server Support .................... SUCCESS [ 1.742 s] [INFO] Log4j API to SLF4J Adapter ......................... SUCCESS [ 3.449 s] [INFO] SLF4J 1 Binding for Log4j API ...................... SUCCESS [ 4.246 s] [INFO] Apache Log4j Cassandra ............................. SUCCESS [ 3.662 s] [INFO] Apache Log4j fuzz tests ............................ SUCCESS [ 2.281 s] [INFO] Apache Log4j Core fuzz tests ....................... SUCCESS [ 1.575 s] [INFO] Apache Log4j Core Integration Tests ................ SUCCESS [ 0.863 s] [INFO] Apache Log4j CouchDB ............................... SUCCESS [ 2.228 s] [INFO] Apache Log4j Docker Library ........................ SUCCESS [ 2.165 s] [INFO] Apache Log4j Streaming Interface ................... SUCCESS [ 5.533 s] [INFO] Apache Log4j Jakarta JMS ........................... SUCCESS [ 3.729 s] [INFO] Apache Log4j Jakarta SMTP .......................... SUCCESS [ 3.281 s] [INFO] Apache Log4j Jakarta Web ........................... SUCCESS [ 4.299 s] [INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [ 2.859 s] [INFO] Apache Log4j JPA ................................... SUCCESS [ 5.001 s] [INFO] Apache Log4j JDK Platform Logging Adapter .......... SUCCESS [ 2.915 s] [INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [ 3.180 s] [INFO] Apache Log4j JUL Adapter ........................... SUCCESS [ 6.863 s] [INFO] Apache Log4j JSON Template Layout .................. SUCCESS [ 4.633 s] [INFO] Apache Log4j JSON Template Layout fuzz tests ....... SUCCESS [ 1.609 s] [INFO] Apache Log4j MongoDB 4 ............................. SUCCESS [ 22.622 s] [INFO] Apache Log4j MongoDB Appender ...................... SUCCESS [ 3.264 s] [INFO] Apache Log4j to JUL Bridge ......................... SUCCESS [ 3.177 s] [INFO] Apache Log4j OSGi tests ............................ SUCCESS [ 4.821 s] [INFO] Apache Log4J Performance Tests ..................... FAILURE [ 0.175 s] [INFO] SLF4J 2 Provider for Log4j API ..................... SKIPPED [INFO] SLF4J 2 Provider for Log4j API fuzz tests .......... SKIPPED [INFO] Apache Log4j Spring Boot Support ................... SKIPPED [INFO] Apache Log4j Spring Cloud Config Client Support .... SKIPPED [INFO] Apache Log4j Web ................................... SKIPPED [INFO] Apache Log4j Tag Library ........................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 03:59 min [INFO] Finished at: 2025-06-15T12:52:51-04:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project log4j-perf-test: Could not resolve dependencies for project org.apache.logging.log4j:log4j-perf-test:jar:2.25.0 [ERROR] dependency: org.apache.logging.log4j:log4j-layout-template-json-test:jar:2.25.0 (compile) [ERROR] Could not find artifact org.apache.logging.log4j:log4j-layout-template-json-test:jar:2.25.0 in central (https://repo.maven.apache.org/maven2) [ERROR] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. I suppose I could cobble up a command line to skip the tests in that one module while keeping the Docker tests enabled elsewhere but I'm satisfied that the MongoDB tests passed in Docker by visual inspection. The ASC and SHA512 files are OK. Gary On Sat, Jun 14, 2025 at 12:16 PM Gary Gregory <garydgreg...@gmail.com> wrote: > > On Sat, Jun 14, 2025 at 11:27 AM Piotr P. Karwasz > <pi...@mailing.copernik.eu> wrote: > > > > Hi Gary, > > > > On 14.06.2025 13:00, Gary Gregory wrote: > > > On Sat, Jun 14, 2025 at 3:09 AM Piotr P. Karwasz > > > <pi...@mailing.copernik.eu> wrote: > > >> I hope this helps you debug what is going on during the ElasticSearch > > >> startup. > > > > > > It appears that port 9200 is published in Docker, but it doesn't seem > > > to be visible outside of Docker, maybe. > > > > > > See https://gist.github.com/garydgregory/a83914942faa2d904bd16966559d07bc > > > > > > Does that ring a bell? > > > > Unfortunately, I don’t see any significant differences between your > > startup logs and mine. On my setup, it ends with: > > > > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Waited on tcp > > port '[/172.19.0.2:9200]' 6521 ms > > > > Whereas yours ends in a timeout: > > > > [ERROR] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Timeout after > > 60739 ms while waiting on tcp port '[/172.19.0.2:9200]' > > > > As for the port binding, the Docker Maven Plugin is configured to bind > > the container port 9200 to an ephemeral host port, assigning it to the > > `elasticsearch.port` Maven property: > > > > <ports> > > <!-- Binds an ephemeral port to the `elasticsearch.port` Maven > > property. --> > > <port>localhost:elasticsearch.port:9200</port> > > </ports> > > > > This assumes that the Docker host is accessible via `localhost`, which > > is valid on Linux, but may not hold on macOS. > > > > You might want to try omitting the host name altogether: > > > > <ports> > > <!-- Binds an ephemeral port to the `elasticsearch.port` Maven > > property. --> > > <port>elasticsearch.port:9200</port> > > </ports> > > Sadly, no love using: > > <port>elasticsearch.port:9200</port> > > [ES]{"@timestamp":"2025-06-14T16:15:37.506Z", "log.level": "INFO", > "message":"closing ...", "ecs.version": > "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch-shutdown","log.logger":"org.elasticsearch.node.Node","elasticsearch.cluster.uuid":"GLSBe1MIRiSH5-Yn083k7Q","elasticsearch.node.id":"ABZT_d4JQbSOLCZlEemDdQ","elasticsearch.node.name":"af7394eff833","elasticsearch.cluster.name":"docker-cluster"} > [ES]{"@timestamp":"2025-06-14T16:15:37.512Z", "log.level": "INFO", > "message":"closed", "ecs.version": > "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch-shutdown","log.logger":"org.elasticsearch.node.Node","elasticsearch.cluster.uuid":"GLSBe1MIRiSH5-Yn083k7Q","elasticsearch.node.id":"ABZT_d4JQbSOLCZlEemDdQ","elasticsearch.node.name":"af7394eff833","elasticsearch.cluster.name":"docker-cluster"} > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Stop and > removed container af7394eff833 after 0 ms > [ERROR] DOCKER> I/O Error [[elasticsearch:8.17.3] "elasticsearch": > Timeout after 60723 ms while waiting on tcp port '[/172.19.0.2:9200]'] > > :( > Gary > > > > > If that works, please submit a PR to fix the issue in > > `log4j-layout-template-json` and `log4j-mongodb`. > > > > Piotr
