Throwing non-WebApplicationException results in IOException: Connection was closed

[gefloh]

Hello,

before opening a bug I wanted to ask if this is an intended behavior: In a RESTEasy resource when I am throwing an exception and this exception is a WebApplicationException or any of its subclasses everything is fine for the client when it's doing retries. When I am throwing something else e.g. a simple RuntimeException, the client gets an expected HTTP 500 at first but if the client does retries, I frequently (but not always) see

2023-11-25 02:24:53,154 DEBUG [org.jbo.res.rea.com.cor.AbstractResteasyReactiveContext] (vert.x-eventloop-thread-0) Restarting handler chain for exception exception: jakarta.ws.rs.ProcessingException: java.io.IOException: Connection was closed
	at org.jboss.resteasy.reactive.client.handlers.ClientSendRequestHandler$4.handle(ClientSendRequestHandler.java:366)
	at org.jboss.resteasy.reactive.client.handlers.ClientSendRequestHandler$4.handle(ClientSendRequestHandler.java:357)

Both applications are local Quarkus 3.5.3 applications. Why is the connection closed? Is it a bug or intended?

Thanks,
Gerhard

[gefloh]

Linked issue #37323.