Quarkus RestClient connectionTTL documentation is misleading #49176
Description
Describe the bug
Hi, documentation for rest client connection TTL quarkus.rest-client.connection-ttl
states
The time in ms for which a connection remains unused in the connection pool before being evicted and closed. A timeout of 0 means there is no timeout.
without mentioning any default value. This doesn't seem to be correct in two points
- values between 1-999 ms effectively sets "no timeout". Based on the implementation any value is divided by 1000 in integer arithmetic, which would result in 0
- no default value is mentioned, when in effect, the default value is 60s based on underlying vertx implementation https://vertx.io/docs/4.5.16/apidocs/io/vertx/core/http/HttpClientOptions.html#DEFAULT_KEEP_ALIVE_TIMEOUT
Expected behavior
Fix the documentation or maybe it would be better using seconds instead of ms as it doesn't look like the vertx implentation supports ttl in ms.
Actual behavior
see above
How to Reproduce?
No response
Output of uname -a or ver
No response
Output of java -version
No response
Quarkus version or git rev
3.20.1
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response