3.13.: All REST requests seem to yield "Unhandled exception in router" without any further info

[famod]

In certain late stages of my project I'm getting:

ERROR [io.ver.ext.web.RoutingContext] (vert.x-eventloop-thread-4) Unhandled exception in router

without any further info/trace. This seems to happen for any REST request aimed towards this Quarkus service.
Scheduled jobs are fine though and I also got past my initial Liquibase issue (see https://issues.apache.org/jira/browse/LANG-1748), so the service is not broken entirely.

Any clue what's going on or any ideas how to get more details? I had a look at the vert.x class involved and I didn't see any debug or trace statements of much value, but I might be wrong.

[famod]

@cescoffier maybe? Thanks!

[cescoffier]

@tsegismont Can you see with @vietj to fix Vert.x Web?

[famod]

understand why we don't get a better error - because not having a clue of what's going on is not a good idea

+ 💯

In that context, I noticed that:
a) access logging doesn't work if this issue strikes (so I had to capture the headers with Quarkus 3.12.2)
b) access logging doesn't have trace id / span id
c) the "Unhandled exception in router" error is also logged without trace id / span id

Maybe none of these issues are solvable because it all happens on such a low level...?

[cescoffier]

I guess it's an NPE - and in this case, we should have a more specific log message (with the stack trace).

[tsegismont]

@tsegismont Can you see with @vietj to fix Vert.x Web?

Sure

[tsegismont]

For the record, I filed vert-x3/vertx-web#2638 and Julien will look into it asap.