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

NoHttpResponseException: <server> failed to respond #71

Closed
stefan-tabakov opened this Issue Oct 7, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@stefan-tabakov

stefan-tabakov commented Oct 7, 2018

When using Gluu with cluster manager and the token expires, the next SCIM-client request causes NoHttpResponseException.
HttpRequestRetryHandler could be added to Reasteasy http client. One possible solution could be to add it in AbstractScimClient:
CloseableHttpClient httpClient = httpClientBuilder.setRetryHandler(new StandardHttpRequestRetryHandler(3, false)).build();

@jgomer2001

This comment has been minimized.

Collaborator

jgomer2001 commented Oct 23, 2018

Hi @stefan-tabakov

I was discussing your problem with cluster manager expert. We see no apparent reason for this behavior in this scenario. Actually, SCIM-Client retries when token is invalid.

It would be great If you could provide us more information about your specific problem. Like sharing some sample code, logs and details of the task you are trying to achieve.

Feel free to open a ticket at support.gluu.org if you wish.

@stefan-tabakov

This comment has been minimized.

stefan-tabakov commented Oct 30, 2018

Hi @jgomer2001 and thanks for your comment.
After some more investigation, I came to the conclusiom the problem I face is not actually related to the token expiration.
One difference between the classical Gluu deployment and the cluster mode is that in cluster mode there is a nginx server in front, acting as reverse proxy. It seems the default timeout in nginx is 300s. After this 300s inactive connections are closed from nginx, however the HttpClient wrapped by the ScimClient doesn't know this and it end-ups with the exception described in the issue.
We finally added the same value of 300s to validate after inactivity configuration of our ConnectionManager, this way cm.setValidateAfterInactivity
May be it's a good idea to add the support of this parameter to the abstract scim client.

@jgomer2001 jgomer2001 added this to the 3.1.5 milestone Oct 30, 2018

@jgomer2001

This comment has been minimized.

Collaborator

jgomer2001 commented Oct 30, 2018

Thanks for the info, we'll review and determine if it's good idea. I milestoned it for 3.1.5

@jgomer2001 jgomer2001 self-assigned this Nov 30, 2018

@jgomer2001

This comment has been minimized.

Collaborator

jgomer2001 commented Nov 30, 2018

Param added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment