Question：have the api support time out ?

[SunStriderxxx]

i want to call the api with specified timeout, can i do it?
or is there a default value for timeout?

[SunStriderxxx]

i found setReadTimeOut and setConnectionTimeOut method in apiclient,
but in api requestJWTUserToken() , a new client was builded,
have the new client a connection-timeout?

[mmallis87]

@SunStriderxxx here are the links for connect timeout and read timeout.

Regarding your remark about the http client being rebuilt, right now there is a limitation where you need to set back the timeout parameters again after you authenticate...ticket DCM-4929 is going to get rid of this limitation (by saving timeout values and using them after authentication). This ticket's priority has been revisited and we should be able to work on it sooner than later. Until then you'll have to reset the timeout values again.

[SunStriderxxx]

@SunStriderxxx here are the links for connect timeout and read timeout.

Regarding your remark about the http client being rebuilt, right now there is a limitation where you need to set back the timeout parameters again after you authenticate...ticket DCM-4929 is going to get rid of this limitation (by saving timeout values and using them after authentication). This ticket's priority has been revisited and we should be able to work on it sooner than later. Until then you'll have to reset the timeout values again.

no, i use the requestJWTUserToken() method to authenticate, it will not affect member variable apiClient and i don't need to set the connection-timeout and read-timeout again.
it just rebulid a local apiclient, which i can't set connection-timeout for it.
i just want to confirm if i can set connection-timeout in requestJWTUserToken() in the future

[h3nkele]

Despite this being a nearly 5-year-old issue, I want to add to that.

We had a long-running issue where our integration of DocuSign 'just stopped' working after some amount of time.
Then we discovered the timeout configuration made use of it; we could confirm that the values were actually used in the observed requests.

BUT our problem on actual systems did not go away ...

After extracting a stack trace dump of a stalled system, we discovered that we are still stuck in an indefinite wait while reading from an HTTP response.

Further investigation led us to the conclusion that:

• We can, in fact, set the timeouts for the 'normal' DocuSign request (like updating an envelope, etc.) via the client's setters.
• We cannot set timeouts for specific function calls (see picture) and their resulting HTTP requests, as they call the function com.docusign.esign.client.ApiClient.buildHttpClient(boolean), which creates a new client, without the timeout configuration, instead of using the configured one, created by the constructor call and the successive calls to the timeout setter functions.
  • 

This is caused by the issue OP discovered.

We solved that issue for ourselves by extending the provided API client and overriding the function 'com.docusign.esign.client.ApiClient.performAdditionalClientConfiguration(ClientConfig)'.