CAMEL-23431: Migrate camel-grpc and camel-mllp tests from AvailablePortFinder to port-0 binding#23037
CAMEL-23431: Migrate camel-grpc and camel-mllp tests from AvailablePortFinder to port-0 binding#23037gnodet wants to merge 5 commits into
Conversation
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
|
@gnodet can you update this PR as it has merge conflicts now |
394bfb7 to
01bdf62
Compare
a1136c6 to
eb67835
Compare
…rtFinder to port-0 binding - Add getLocalPort() to GrpcConsumer to expose OS-assigned port - Allow port 0 in GrpcConsumer by changing port check from > 0 to >= 0 - Add getLocalPort() to MllpTcpServerConsumer to expose OS-assigned port - Migrate all grpc and mllp tests to use port 0 instead of AvailablePortFinder Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…hread The serverSocket field is package-private, so access it via a public getter instead of direct field access from MllpTcpServerConsumer. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
c660cc9 to
66a347e
Compare
…stion gRPC uses java.util.logging internally and without a logging.properties config, all gRPC framework messages go to console at INFO level, filling the CI runner's diagnostic log and causing disk space failures. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
66a347e to
a8a71b7
Compare
|
Jobs are failing with: |
Yeah, I know. A log file is being filled with stack traces in a tight loop, so it quickly fills up disk space. I need to investigate. |
CAMEL-23431
Migrate
camel-grpcandcamel-mllptests fromAvailablePortFinderto port-0ServerSocketbinding, eliminating TOCTOU race conditions that can cause flakyBindExceptionfailures.Changes
camel-grpc
getLocalPort()toGrpcConsumerto expose the OS-assigned port after server start> 0to>= 0to allow port 0 (OS-assigned)camel-mllp
getLocalPort()toMllpTcpServerConsumerto expose the OS-assigned portTest plan