Rest Client exausts Threads.

[brunobat]

Describe the bug

This is a major issue for us.
I have dozens of services in prod that from time to time they freeze due to thread exhaustion. The vertex event loop stalls.
his can be traced back to unconfigured timeouts on rest clients that hog connections.
We need to go to all rest clients and specify connection and read timeouts on configurations, like:

com.td.wfm.common.client.SomeRestClientClass/mp-rest/connectTimeout=500
com.td.wfm.common.client.SomeRestClientClass/mp-rest/readTimeout=1000

If you use programatic rest creation you must:

        return RestClientBuilder.newBuilder()
                                .baseUri(URI.create(uri))
                                .connectTimeout(connectionTimeout, TimeUnit.MILLISECONDS)
                                .readTimeout(readTimeout, TimeUnit.MILLISECONDS)
                                //...

There are many issues related with this. See:
#15056
#15383
#15191

This happens on 1.13.7.Final but I believe 2.* suffers from the same problem.

Expected behavior

If the REST Client connection is half closed in the other side, it will timeout after a default amount of time.

Actual behavior

If the REST Client connection is half closed in the other side it will never timeout.

How to Reproduce?

You need a rest client calling an endpoint in a loop, in different threads. The other side must hold the connection and not reply.

Output of uname -a or ver

No response

Output of java -version

11

GraalVM version (if different from Java)

No response

Quarkus version or git rev

1.13.7.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @michalszynkiewicz

[geoand]

I assume you are using quarkus-rest-client. Have you tried with quarkus-rest-client-reactive?

[TomasHofman]

I think I can add the same default timeouts that the reactive client uses as part of #22872.

[radcortez]

I think it could be interesting to have a global timeout for REST clients (like we have other properties that set global configuration for clients).

[michalszynkiewicz]

that's a cool idea

[geoand]

I think it could be interesting to have a global timeout for REST clients (like we have other properties that set global configuration for clients).

Definitely

[TomasHofman]

Would something like #22942 be OK?

[brunobat]

This is ok. Thanks @gsmet !