Dispatch back to IO thread for non blocking requests

[stuartwdouglas]

No description provided.

[geoand]

I was thinking of the same thing actually.

My only question is, does this actually get you back to the same Event Loop thread that security was one?

[stuartwdouglas]

It gets you back to the requests event loop thread, security is run on a worker thread. Because this uses the context from the connection it is guaranteed to be the same thread.

[geoand]

Right, I meant the Security filter that could lead to the dispatch to the worker thread.

Sounds good

[geoand]

We would likely need to do something similar in Reactive Routes, but I assume that can wait since we are deprecating them

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 649d2c7

Status	Name	Step	Failures	Logs	Raw logs
✖	JVM Tests - JDK 11	Build	Failures	Logs	Raw logs
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 #

- Failing: integration-tests/resteasy-reactive-kotlin/standard 

📦 integration-tests/resteasy-reactive-kotlin/standard

✖ io.quarkus.it.resteasy.reactive.kotlin.FlowResourceTest.testSseStrings line 22 - More details - Source on GitHub

java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1886)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021)

✖ io.quarkus.it.resteasy.reactive.kotlin.FlowResourceTest.testSuspendSseStrings line 29 - More details - Source on GitHub

java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1886)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021)

✖ io.quarkus.it.resteasy.reactive.kotlin.FlowResourceTest.testSeeJson line 36 - More details - Source on GitHub

java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1886)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021)

---

⚙️ JVM Tests - JDK 17 #

- Failing: integration-tests/resteasy-reactive-kotlin/standard 

📦 integration-tests/resteasy-reactive-kotlin/standard

✖ io.quarkus.it.resteasy.reactive.kotlin.FlowResourceTest.testSseStrings line 22 - More details - Source on GitHub

java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095)

✖ io.quarkus.it.resteasy.reactive.kotlin.FlowResourceTest.testSuspendSseStrings line 29 - More details - Source on GitHub

java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095)

✖ io.quarkus.it.resteasy.reactive.kotlin.FlowResourceTest.testSeeJson line 36 - More details - Source on GitHub

java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095)

[stuartwdouglas]

@geoand I needed to do this to make the kotlin tests work. Not sure if I like it much but I think it is probably ok for now.

[geoand]

I think we can live with it :)