You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "jam01 (via GitHub)" <gi...@apache.org> on 2025/11/16 01:11:30 UTC
[I] camel-quarkus-examples/aws-lambda does not run [camel-quarkus]
jam01 opened a new issue, #7973:
URL: https://github.com/apache/camel-quarkus/issues/7973
### Description
The aws-lambda example does not run in dev mode because the dev-ui console is taking the 8080 port. This is seemingly not an issue with plain quarkus http server apps, but it seems the lambda mock server does not play well with the dev-ui (assuming it's based on vertx features).
It'd seem to me this should be documented _somewhere_.
Reproduced by
```bash
git clone git@github.com:apache/camel-quarkus-examples.git
cd camel-quarkus-examples/aws-lambda/
mvn quarkus:dev
```
results in
```text
2025-11-15 18:43:01,856 INFO [io.qua.ama.lam.run.AbstractLambdaPollLoop] (Lambda Thread (DEVELOPMENT)) Listening on: http://localhost:8080/_lambda_/2018-06-01/runtime/invocation/next
2025-11-15 18:43:01,966 WARN [io.qua.ama.lam.run.AbstractLambdaPollLoop] (Lambda Thread (DEVELOPMENT)) Aborting lambda poll loop: ending dev/test mode
2025-11-15 18:43:01,968 INFO [io.qua.ama.lam.run.AbstractLambdaPollLoop] (Lambda Thread (DEVELOPMENT)) Lambda polling thread complete (DEVELOPMENT)
2025-11-15 18:43:01,970 INFO [org.apa.cam.imp.deb.DefaultBacklogDebugger] (Quarkus Main Thread) Disabling Camel debugger
2025-11-15 18:43:01,970 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Apache Camel 4.15.0 (camel-1) is shutting down
2025-11-15 18:43:01,978 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Routes stopped (total:1)
2025-11-15 18:43:01,979 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Stopped Test (direct://input)
2025-11-15 18:43:01,988 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Apache Camel 4.15.0 (camel-1) shutdown in 17ms (uptime:0s)
2025-11-15 18:43:01,997 ERROR [io.qua.run.Application] (Quarkus Main Thread) Port 8080 seems to be in use by another process. Quarkus may already be running or the port is used by another application.
```
--
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: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] camel-quarkus-examples/aws-lambda does not run [camel-quarkus]
Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton commented on issue #7973:
URL: https://github.com/apache/camel-quarkus/issues/7973#issuecomment-3538427589
I don't see the 'port in use by another process' message, the app starts ok for me. But, the dev-ui is not accessible.
You can get around it by configuring the mock server ports:
```
quarkus.lambda.mock-event-server.dev-port=8082
quarkus.lambda.mock-event-server.test-port=8083
```
All of this behaviour is controlled by the `quarkus-aws-lamdba` extension. So it'd be better to create a [Quarkus issue](https://github.com/quarkusio/quarkus/issues) if you'd like it to be investigated.
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org