NetBurner TCP active connection limitation?

Discussion to talk about software related topics only.
Post Reply
mokie
Posts: 9
Joined: Mon Jul 19, 2010 6:42 am

NetBurner TCP active connection limitation?

Post by mokie »

I'm using a MOD5282 and am establishing many TCP connections (specifially in using FTPGetList, FTPGetFileNames, FTPGetFile, FTPSendFile) at once (over 255). Once it gets to the 255th TCP connection, FTPGetCommandResult will error out and say the socket is already in use since the previous 255 active TCP connections in the TIME_WAIT state have not yet had a chance to expire. If I put in a delay until the TIME_WAIT state is up (about 25 seconds), then I can open 255 new TCP connections. Is 255 indeed a limit on the active TCP connections and is there anyway to increase this limit?

P.S. This is my previous post on a related topic (TIME_WAIT): http://forum.embeddedethernet.com/viewt ... ?f=5&t=842
User avatar
pbreed
Posts: 1088
Joined: Thu Apr 24, 2008 3:58 pm

Re: NetBurner TCP active connection limitation?

Post by pbreed »

Sounds like an issue with the server not the netburner.
The Netburner only has 32 TCP sockets.


What are you connecting to?

Can you do the same exact test from a PC?

Paul
Post Reply