Prevent ContextNotActiveException during invalid config validation if resteasy-reactive module is present

[luca-bassoricci]

Check for an active RequestContext before accessing ResteasyReactiveLocaleResolver#currentVertxRequest to prevent ContextNotActiveException

I addes only 1 test in integration-tests\hibernate-validator-resteasy-reactive module because extensions\hibernate-validator\deployment doesn't use resteasy-reactive which is a mandatory module to raise the problem.

I'm also looking to reproduce the problem in our backend code with some @RestClients interaction but takes time.

Fixes #31434

[quarkus-bot]

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

• title should not contain an issue number (use Fix #1234 in the description instead)

This message is automatically generated by a bot.

[gsmet]

I can't say if it's the right fix but given what you described in #31434, I think you are onto something that needs fixing.

/cc @geoand who can probably provide some useful guidance (@geoand see the issue for a description of the problem)

[geoand]

We seem to also have #31544 which attempts to fix the problem

[geoand]

I think the approach taken in this PR here makes more sense

[gsmet]

@luca-bassoricci I force pushed to your branch to fix the formatting issue.

[luca-bassoricci]

@luca-bassoricci I force pushed to your branch to fix the formatting issue.

Grazie :)
I ran the formatter:format from my command shell and I thought imports were ordered, but I was wrong.

[luca-bassoricci]

I can't say if it's the right fix but given what you described in #31434, I think you are onto something that needs fixing.

/cc @geoand who can probably provide some useful guidance (@geoand see the issue for a description of the problem)

quarkus/extensions/hibernate-orm/runtime/src/main/java/io/quarkus/hibernate/orm/runtime/tenant/HibernateCurrentTenantIdentifierResolver.java

Lines 29 to 35 in a74aa01

	public String resolveCurrentTenantIdentifier() {
	// Make sure that we're in a request
	if (!Arc.container().requestContext().isActive()) {
	return null;
	}

I used this kind of solution because I found it was used elsewhere.

[quarkus-bot]

Failing Jobs - Building da65125

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 17
✔️	JVM Tests - JDK 19

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 Windows #

- Failing: extensions/reactive-routes/deployment 
! Skipped: extensions/resteasy-reactive/quarkus-resteasy-reactive-jackson/deployment extensions/resteasy-reactive/quarkus-resteasy-reactive-jaxb/deployment extensions/resteasy-reactive/quarkus-resteasy-reactive-jsonb/deployment and 9 more

📦 extensions/reactive-routes/deployment

✖ io.quarkus.vertx.web.context.DuplicatedContextTest.testThatRoutesAreCalledOnDuplicatedContext line 58 - More details - Source on GitHub

io.smallrye.mutiny.TimeoutException
	at io.smallrye.mutiny.operators.uni.UniBlockingAwait.await(UniBlockingAwait.java:64)
	at io.smallrye.mutiny.groups.UniAwait.atMost(UniAwait.java:65)