-
-
Notifications
You must be signed in to change notification settings - Fork 548
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
Unexpected socket closing, round#2 #348
Comments
I'm sorry, I've only seen this issue today. This is indeed really odd, thanks for reporting! I'll see if I can reproduce this. |
I'm not able to reproduce this here on Linux. Are you running the server on macOS? |
Hi, no problem, I also haven't enough time for this problem. Today I tested it with latest master, it's still available. I used Ubuntu, usually I use this distribution to getting closer to the release time. Last log:
|
Hi,
I found an other weird behaviour in Lwan when I started to use our server for serving video streams for masses. After a point, when the client drop the connection, for example it had a network issue, it's connection stuck in the queue and start closing its socket after that connection was dropped.
Steps for reproducing:
hello
sample app.Server output will be something like this:
This means connections were closed by test application abort well. Until this everything went fine.
After keep-alive timeout reached Lwan starts sending these messages:
Unfortunately this means sometimes that close() in the timeout_queue_expire() function hit another valid connection was created by another http request.
After I reverted back this commit (7a8a0eb) everything get back to normal.
Thanks,
pontscho
The text was updated successfully, but these errors were encountered: