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

CometD Long Polling takes longer than timeout value #837

Open
jaypatel512 opened this Issue Mar 5, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@jaypatel512
Copy link

jaypatel512 commented Mar 5, 2019

Hey all,

I have a timeout set for cometD long polling as 60000ms (60 seconds). And client is configured to have a socketTimeout as 62000ms (62 seconds). We are seeing socketTimeout in some cases, where our long polling client goes above 60000ms. Am I missing something here ? How can the socketTimeout be calculated to ensure we do not get a timeout via socket in normal cases.

@sbordet

This comment has been minimized.

Copy link
Member

sbordet commented Mar 5, 2019

The server should always timeout at 60 seconds. The client may see more than that because of network roundtrips, so perhaps you have a really bad network?
Also, if the connection is dropped for any reason, the client may timeout because the server cannot write back to the client.

Do you have DEBUG logs that show this behavior?

@jaypatel512

This comment has been minimized.

Copy link
Author

jaypatel512 commented Mar 11, 2019

Unfortunately not, as this is seen in production only.

@sbordet

This comment has been minimized.

Copy link
Member

sbordet commented Mar 11, 2019

Could be Full GC taking many seconds?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.