urunni88 opened a new pull request, #28284:
URL: https://github.com/apache/camel/pull/28284

   # Description
   
   Fixes [CAMEL-25697](https://issues.apache.org/jira/browse/CAMEL-25697).
   
   `BonitaAuthFilterConnectionTest` started WireMock with 
`WireMockConfiguration.options()` and no port, so WireMock used its default 
port 8080. When another process or test held port 8080, the setup failed with 
`Failed to bind to /0.0.0.0:8080` (`Address already in use`).
   
   The fix uses `WireMockConfiguration.options().dynamicPort()`, as 
`BonitaStartCaseFileUploadTest` and `BonitaStartProducerClientTest` already do. 
The tests already read the port with `wireMockServer.port()`, so nothing else 
changes.
   
   Verified locally by holding port 8080 open while running the test:
   - before the change: both tests fail with `Failed to bind to /0.0.0.0:8080`, 
the same error as in CI
   - after the change: both tests pass
   
   All 25 camel-bonita tests pass.
   
   This PR was prepared with AI assistance (Claude); I reviewed and tested all 
changes.
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   - [x] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   # AI-assisted contributions
   
   - [x] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.


-- 
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]

Reply via email to