From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Problem when lots of sockets open.
Date: Thu, 08 Mar 2001 17:28:00 -0000 [thread overview]
Message-ID: <20010308193311.A3634@visi.com> (raw)
I've got an eCos app that listens for TCP connections on 16
different ports.
I can connect to any 8 of them, but usually the 9th TCP
connection opens and is then immediately closed by the eCos
stack: the eCos system sends a FIN exactly 50ms after the 2nd
SYN is ack'ed. I've added some diag_printfs to figure out
where the socket is getting closed, and pretty sure it's not me
calling close().
I've also seen situations where there are 8 open sockets, and
the 9th connect succeeds but kills one of 8 previously open
sockets.
I did have to increase the number of open files allowed from 16
to 32. Since I never get to socket 31, I don't think that's the
problem this time.
Is there another limit somewhere I need to increase to get more
than 8 open TCP connections? I don't see anything in ecos.ecc
that looks like a limit on TCP connections.
--
Grant Edwards
grante@visi.com
next reply other threads:[~2001-03-08 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 17:28 Grant Edwards [this message]
2001-03-09 5:30 ` Lewin A.R.W. Edwards
2001-03-09 7:13 ` Grant Edwards
2001-03-12 8:22 ` Grant Edwards
2001-03-12 10:42 ` Grant Edwards
2001-03-12 12:27 ` Gary Thomas
2001-03-12 12:35 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010308193311.A3634@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).