-
Notifications
You must be signed in to change notification settings - Fork 284
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
Exception@../source/vibe/core/drivers/libevent2_tcp.d(287): Operating on closed TCPConnection. #43
Comments
ab -n 10000 -c 1000 http://192.168.2.3:8080/ <=== _FIXED_: #44, 10aba8f3117 Nginx reverse proxy:
|
Can you recheck if this still occurs? From the log output I think it is fixed with the previous commit. |
Ok thanks, I'll close the issue then for now. |
Turns out this is still happening. Easy to reproduce in Chrome with pipelining enabled or Firefox with pipelining enabled. It was happening less but I still get it all the time. -[Unknown] |
…P connections - should fix the remaining part of issue #43.
Turned out that TcpConnection.close() was not working correctly. It's somehow rediculous how difficult such things can be to get right with libevent-like libraries compared to bare metal socket code - caused by hidden state that they introduce and which is not really documented. |
ab -n 10000 -c 1000 http://127.0.0.1:8080/ <=== _OK_ (localhost)
ab -n 10000 -c 1000 http://192.168.2.3:8080/ <=== _EXCEPTION!!!_
_Nginx reverse proxy:
ab -n 10000 -c 1000 http://192.168.2.3/ <=== _EXCEPTION!!!
ab -n 10000 -c 1000 http://127.0.0.1/ <=== _EXCEPTION!!!_
No problem with node.js, tornado or g-wan.
The text was updated successfully, but these errors were encountered: