-
-
Notifications
You must be signed in to change notification settings - Fork 540
connection timed out after few minutes #110
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
Comments
You should wrap If the timeout is reached, I suggest using 25 seconds for the timeout as many systems close idle connections after 30 seconds. (I'm interested in hearing whether that solution actually works. Perhaps I should document it better.) |
@aaugustin are you talking about |
Yes, that's the easier way to achieve the desired timeout here. I thought it was added in Python 3.5 but apparently it also exists in 3.4 (and I don't think 3.3 matters much these days). |
My python version is 3.5 so, It won't be a problem for me. I will test this ASAP. |
I solved this issue as you suggested. Thanks. Case closed now. |
Actually I'd like to keep this issue around to check if I can improve documentation. |
@aaugustin: Actually i'll (and others) appreciate if you can document this subject as you stated. In fact, I fixed already but still need some document to check if i did the correct way. |
This will be built-in if #449 gets merged. |
I have a definition like this:
And few minutes later if i stay idle i get this on server and disconnect user:
How can avoid this and stay connected as long as possible?
The text was updated successfully, but these errors were encountered: