Improve JFR integration in Quarkus REST

[geoand]

We are now able to capture events for all
HTTP requests that are meant to be handled
by Quarkus REST, whether they were successfully
handled or not.

• Fixes: quarkus-jfr can cause a NullPointerException #44976

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 21a9657.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[geoand]

🙏🏽

[andrewazores]

Can/will this be backported to 3.15?

[geoand]

Unfortunately it's a little too risky for 3.15. What we can do for 3.15 is have a dedicated bug fix that will just prevent the NPE for occuring

[andrewazores]

Sounds good. So for 3.15 there will still not be a JFR event recorded, but the original expected status code (ex. 404, 405, 406) will be sent?

[geoand]

Yeah, that's correct.

[geoand]

@gsmet do you have a rough idea when we plan to do another 3.15?

[andrewazores]

A fix didn't make it into 3.15.3, did it? I don't see a mention of it in the changelog, but maybe I'm just missing it.

[geoand]

Yeah, that was my bad. I'll make sure we get it in for 3.15.4

[andrewazores]

Thanks!

[geoand]

Sorry for missing this :(

[andrewazores]

@geoand any hint on when 3.15.4 might release?

[geoand]

The current plan can be found here