Using Dev ui "breaks" a lambda

[steven-ww]

Describe the bug

When using the Quarkus lambda extension, rest endpoints are available/usage until you load the dev UI. Once you've git the dev-ui endpoint, all calls to the rest endpoints timeout.

Expected behavior

The rest endpoints should return results as normal.

Actual behavior

Timeouts when calling the rest endpoint.

How to Reproduce?

https://github.com/DragonMaster337/TopicBackend1

The main branch has Quarkus 2.14.3, but this also fails in Quarkus 3.1.2-final.

Checkout the main branch
Build mvn clean install
run dev mode mvn quarkus:dev

1. Hit the localhost endpoint HTTP://localhost:8080/hello?name=Bob

You should get a "Hello Bob!" response.

2. Hit the dev-ui endpoint http://localhost:8080/q/dev/

The dev UI comes up.

3. Hit the initial URL again,

No response/timeout.

Output of uname -a or ver

Darwin Stevens-MacBook-Pro.local 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000 arm64

Output of java -version

openjdk version "17.0.5" 2022-10-18 LTS OpenJDK Runtime Environment Corretto-17.0.5.8.1 (build 17.0.5+8-LTS) OpenJDK 64-Bit Server VM Corretto-17.0.5.8.1 (build 17.0.5+8-LTS, mixed mode, sharing)

GraalVM version (if different from Java)

N/A

Quarkus version or git rev

2.14.3.Final or 3.1.2.Final

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.2

Additional information

The requests do seem to hit Quarkus, but just never return...

[quarkus-bot]

/cc @cescoffier (devui), @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda), @phillip-kruger (devui)

[steven-ww]

If you want to recreate with Quarkus 3.1.2-Final, use branch dynamodb2. (It also has an addition ext configured for dynamodb)

[cescoffier]

Can you provide a minimal reproducer with just what's required to reproduce?

[patriot1burke]

Dev UI doesn't work with Lambda. Long standing issue with the way Dev UI is implemented.

[cescoffier]

It might become better with the new one as we removed the virtual server.

[cescoffier]

(unfortunately, because we have both, the issue might still be present - until we get rid of the first dev UI)

[phillip-kruger]

@cescoffier can we close this now ?

[cescoffier]

No, we must verify first.

[phillip-kruger]

@steven-ww if you keen you can test with latest CR release and let us know ?

[steven-ww]

Yeah, sure. I’ll have a look and update with my findings.

…

On 13 Sep 2023, at 07:21, Phillip Krüger ***@***.***> wrote: @steven-ww <https://github.com/steven-ww> if you keen you can test with latest CR release and let us know ? — Reply to this email directly, view it on GitHub <#34285 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APRCYWMTNONFM4PRBXAC5YDX2E7HFANCNFSM6AAAAAAZRW2YYE>. You are receiving this because you were mentioned.

[steven-ww]

@phillip-kruger I tested (sorry it took so long) with Quarkus 3.4.1 and the issue is still there.

[phillip-kruger]

Thanks @steven-ww ! @cescoffier f.y.i.

I'll have a look a.s.a.p

[phillip-kruger]

@cescoffier I am not sure how to fix this to be honest. We are going to need aws extension maintainers to help.

[cescoffier]

Ok, I will try to have a look soonish.

[phillip-kruger]

What I figured out is if you remove the virtual server, everything works. Without it, only the virtual server is started and the normal vertx server not, so dev-ui does not work. We either need to use the normal vertx server (maybe dev mode only) or also serve the dev ui from the virtual one. Or allow both.

[nicklasweasel]

Is this also why swagger-ui appears to show nothing (3.8.2) with the lambda extension present?

[phillip-kruger]

Yes that could be.