netty reset the connection when client do the Retarnsmission

[Trustin Lee (이희승)]

Although Vista SP3 removed such restriction, I still see random
connection failure and I don't know why.  What's interesting is
retrying the connection attempt just works around the problem.  I also
increased the backlog of the server socket, but it did not help.

HTH

— Trustin Lee, http://gleamynode.net/



On Tue, Nov 3, 2009 at 11:41 PM, Huican Ping <pinghuican at gmail.com> wrote:
>
> Hello Trustin,
>
> I think it is a Windows OS issue, and Windows Genius set some limit
> for maximum allowed concurrent in a second.
> At first they normally set this limit as 10, and I get rid of this 10
> from the registery, and it still shows it limits about 50. Then I
> really have no idea how to break this about 50 limit in a second. Do
> you have any idea about it?
>
> FYI, this limit of maximum 50 concurrent connections forces me to
> slowly increase the connections if I want to have large number
> concurrent connection.
>
> Really it seems not related to netty.
>
> Thanks for your reply.
>
> Huican
>
>
> On Tue, Nov 3, 2009 at 2:39 AM, Trustin Lee [via Netty Forums and
> Mailing Lists] <ml-node+3937180-1784771745 at n2.nabble.com> wrote:
>> Hi Huican,
>>
>> Sorry for a late response first of all.
>>
>> I wonder if this issue is specific to Windows or reproduceable in
>> other platforms such as Linux.  Could you let me know?
>>
>> Thanks
>>
>> — Trustin Lee, http://gleamynode.net/
>>
>> On Wed, Oct 7, 2009 at 5:04 AM, Huican Ping <[hidden email]> wrote:
>>>
>>> Hello Trustin,
>>>
>>> we noticed an issue When sending a large number of threads with small
>>> messages, the netty Input server
>>> for windows is resetting the TCP connection on a lot of the requests.
>>> Changing to a large file size does not show the issue.  So it seems the IS
>>> is not handling the high rate of connection turnover with the small
>>> messages.
>>>
>>> Using tcpdump, we captured some tcp packages, and it seems the client does
>>> a
>>> retransmission of the data, and the netty Input server comes back
>>> immediately with a reset.  It appears to have not liked the
>>> retransmission.
>>>
>>> I attached that tcpdump file.
>>>
>>> Thanks
>>> HP
>>>
>>>
>>> http://n2.nabble.com/file/n3777791/retransmission_causeNettyDropConnection.cap
>>> retransmission_causeNettyDropConnection.cap
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/netty-reset-the-connection-when-client-do-the-Retarnsmission-tp3777791p3777791.html
>>> Sent from the Netty User Group mailing list archive at Nabble.com.
>>> _______________________________________________
>>> netty-users mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/netty-users
>>>
>> _______________________________________________
>> netty-users mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/netty-users
>> — Trustin Lee, http://gleamynode.net/
>>
>> ________________________________
>> View message @
>> http://n2.nabble.com/netty-reset-the-connection-when-client-do-the-Retarnsmission-tp3777791p3937180.html
>> To unsubscribe from netty reset the connection when client do the
>> Retarnsmission, click here.
>>
>
> --
> View this message in context: http://n2.nabble.com/netty-reset-the-connection-when-client-do-the-Retarnsmission-tp3777791p3938848.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>