Description
Describe the bug
When using spring.cloud.azure.keyvault.secret a connect-timeout can be confgured in three variants:
- spring.cloud.azure.client.http.connect-timeout (configuration-properties-global)
- spring.cloud.azure.keyvault.client.connect-timeout (configuration-properties-azure-key-vault)
- spring.cloud.azure.keyvault.secret.client.connect-timeout (configuration-properties-azure-key-vault-secrets)
When using a configuration which triggers an io.netty.channel.ConnectTimeoutException
the timeout for this is only correctly set when using variant 3. When using variant 1 or 2, the timeout stays at the default 10 seconds.
Exception or Stack Trace
log_global.txt
To Reproduce
- Configure usage of Azure keyvault secrets
- Configure the connect-timeout with variant 1 or 2 (see above).
- Introduce an error in the config (like URI to nonexistent key vault).
Expected behavior
The configured timeout should be used when it is configured globally (variant 1) or for Azure keyvault (variant 2).
Setup (please complete the following information):
- OS: MacOs 14.7.1
- Library/Libraries: com.azure.spring:spring-cloud-azure-starter-keyvault-secrets:4.90 via com.azure.spring:spring-cloud-azure-dependencies:5.18.0
- Java version: 23
- Frameworks: Spring Boot
If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError
, NoSuchMethodError
or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:
- verbose dependency tree (
mvn dependency:tree -Dverbose
) - exception message, full stack trace, and any available logs
Additional context
#31051 seems to be similar
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
- Bug Description Added
- Repro Steps Added
- Setup information Added
Metadata
Metadata
Assignees
Labels
Type
Projects
Status