-
Notifications
You must be signed in to change notification settings - Fork 461
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
client socket time out #1
Comments
Hi, I cannot help you with that just yet. I will need to look into all that Oh, and if you find a solution before then, please let me know!
On Fri, Nov 20, 2015 at 1:46 PM, whutjs [email protected] wrote:
Jakob Jenkov Jenkov Aps |
I cannot help you with that just yet. I will need to look into all that Oh, and if you find a solution before then, please let me know!
On Fri, Nov 20, 2015 at 1:46 PM, whutjs [email protected] wrote:
Jakob Jenkov Jenkov Aps http://feeds2.feedburner.com/jenkov-com —Reply to this email directly or view it on GitHub. |
I'm still studying the sources, but I have a guess: When HttpMessageReader.read() calls Message.writeToMessage(), and there is no space for the new content, and no free block to expand, then the content of the ByteBuffer will be lost. (just a guess, didn't tried) |
Hi, jjenkov, I really appreciate you blog because I've learned how to use Java NIO.And I have written a Http server based on your code.It works well when there are not much connections.But when I test it with high concurrent connection(10K connection), almost all the connections are time out(Socket time out). I just don't know how to optimize it now. Could you give me some advice? Thanks anyway!
The text was updated successfully, but these errors were encountered: