[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [lwip-users] TCP causing out of mem pool [RAW]
From: |
Bill Auerbach |
Subject: |
RE: [lwip-users] TCP causing out of mem pool [RAW] |
Date: |
Tue, 28 Jul 2009 08:16:24 -0400 |
Chris, are you using FireFox? I read somewhere that FireFox opens a
connection for each item on a WEB page, whereas IE doesn't. I've seen other
people complain that embedded WEB servers can't handle all of the connection
attempts with FireFox.
Bill
>-----Original Message-----
>From: address@hidden
>[mailto:address@hidden On
>Behalf Of Chris_S
>Sent: Tuesday, July 28, 2009 7:41 AM
>To: Mailing list for lwIP users
>Subject: Re: [lwip-users] TCP causing out of mem pool [RAW]
>
>TCP dies after that. This is a real problem.
>
>I tried changing TCP_MSL from 60000 to 6000,
>and it sure had an effect. I saw some TCB blocks being reallocated,
>but again after more refreshes it finally crashed the CPU and went to
>restart.
>
>I had KEEPALIVE turned ON, and tried it OFF, still the same.
>
>I noticed an old bug 24830 that seems like the same thing.
>Not fixed yet, says v1.4
>
>I'm just mystified how people get this RAW working with this kind of a
>problem.
>Are there some special settings in lwipopts.h to deal with this?
>Is this something I can bandaid in my HTTPd? Is that what people do?
>
>Chris.
>
>
>
>
>> On Tue, 2009-07-28 at 04:03 -0700, Chris_S wrote:
>> > > > Obviously the TCP PCB is never being freed.
>> > > > So what routine is suppose to do this?
>> > >
>> > > They're probably all in the TIME_WAIT state. This is correct.
>They'll
>> > > get freed once they leave TIME_WAIT and go to CLOSED.
>> > >
>> > > Kieran
>> >
>> > So when do they go to CLOSED?
>> > I waited minutes and the TCP pile keeps building.
>> > I closed my browser window, opened another,
>> > and the TCP still keeps piling up.
>> >
>> > Not happening. When do they get freed?
>>
>> 2 * TCP_MSL is the default timeout I think.
>>
>> However, I think we try and recycle PCBs from TIME_WAIT when we try to
>> alloc and there isn't one available. I wonder if the message you're
>> seeing is just the "I failed to find a free one" and then the
>following
>> line of code gets one from TIME_WAIT and everything is OK. Do you
>> actually see anything go wrong, or is it just the message that you
>don't
>> like?
>
>
>
>_______________________________________________
>lwip-users mailing list
>address@hidden
>http://lists.nongnu.org/mailman/listinfo/lwip-users
- [lwip-users] tcp_listen_with_backlog [RAW], Chris_S, 2009/07/27
- Re: [lwip-users] tcp_listen_with_backlog [RAW], Kieran Mansley, 2009/07/27
- Re: [lwip-users] tcp_listen_with_backlog [RAW], Chris_S, 2009/07/27
- Re: [lwip-users] tcp_listen_with_backlog [RAW], Kieran Mansley, 2009/07/27
- [lwip-users] TCP causing out of mem pool [RAW], Chris_S, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Kieran Mansley, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Chris_S, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Kieran Mansley, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Chris_S, 2009/07/28
- RE: [lwip-users] TCP causing out of mem pool [RAW],
Bill Auerbach <=
- Re: [lwip-users] TCP causing out of mem pool [RAW], Chris_S, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Kieran Mansley, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Chris_S, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Kieran Mansley, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Chris_S, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], address@hidden, 2009/07/28
- RE: [lwip-users] TCP causing out of mem pool [RAW], Roger Cover, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], address@hidden, 2009/07/28
- RE: [lwip-users] TCP causing out of mem pool [RAW], Bill Auerbach, 2009/07/28
- Re: [lwip-users] TCP causing out of mem pool [RAW], Chris_S, 2009/07/28