Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question:have the api support time out ? #173

Open
SunStriderxxx opened this issue Nov 4, 2020 · 3 comments
Open

Question:have the api support time out ? #173

SunStriderxxx opened this issue Nov 4, 2020 · 3 comments
Labels
area-java version specific Different behavior depending on the Java version bug DCM-4929 ticketed

Comments

@SunStriderxxx
Copy link

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

@SunStriderxxx
Copy link
Author

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 mmallis87 added area-java version specific Different behavior depending on the Java version bug ticketed DCM-4929 labels Nov 12, 2020
@mmallis87
Copy link
Contributor

@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
Copy link
Author

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-java version specific Different behavior depending on the Java version bug DCM-4929 ticketed
Projects
None yet
Development

No branches or pull requests

2 participants