Custom Timeout Configuration for Long-Running APIs in digiRunner #70
-
|
Hello, I’m currently testing an API through digiRunner that takes over a minute to respond. However, it appears that there is a gateway timeout being enforced, likely before the API has a chance to complete. I’d like to ask if there is any way to configure or extend the timeout limit within digiRunner to support long-running API requests. If such a setting exists—either in the UI, environment configuration, or elsewhere—I'd appreciate any guidance on how to adjust it. Thank you in advance for your support. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hello, thank you for using this. There are three ways to change the connection timeout:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the support! |
Beta Was this translation helpful? Give feedback.
Hello, thank you for using this.
Yes, there is a setting that can be changed.
The current system default timeout is 30 seconds.
There are three ways to change the connection timeout:
httpClient.connection.timeout=30000
OS Environment:
-e HTTPCLIENT_CONNECTION_TIMEOUT=30000
JVM Argument (override Docker CMD):
-DhttpClient.connection.timeout=30000