davsclaus opened a new pull request, #29509:
URL: https://github.com/apache/camel/pull/29509
_Claude Code on behalf of davsclaus_
Found while running the examples one after another. `connect/http-client`
serves HTTP on 8080, and so does `contracts/openapi-server`. With the first one
running, the second fails to start, and its failure log opened at the end of a
long stack trace, with `java.net.BindException: Address already in use`
somewhere in it.
The failure log now starts with a hint:
```
✗ Port 8080 is in use: the running integration http-client (pid 485107)
serves HTTP on it.
Stop it first, or give this integration another port:
camel.server.port=8081 in its application.properties.
```
- **The port:** read from the error (`on 0.0.0.0:8080`).
- **The owner:** a running integration that consumes HTTP (`platform-http`
or the REST DSL) and is configured for that port, from `camel.server.port` in
its directory's `application.properties`, or 8080, Camel's default, when that
isn't set. When none is, the hint says another program has the port.
- **Where it shows:** the log then opens at the top, where the hint is.
`tui_run_example` gives an AI agent the same hint in a `hint` field of its
failure answer.
The new class is `PortInUse`.
Tests: `PortInUseTest`. The full `camel-jbang-plugin-tui` suite passes,
apart from `ConfigurationTabRenderTest`, which fails on main and is fixed by
#29503. I checked it live by running the two examples.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
