From: Michael Sig Birkmose <michael@gisp.dk>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Problems with sockets after 1132 requests
Date: Tue, 02 Dec 2003 11:59:00 -0000 [thread overview]
Message-ID: <20031202131549.Y54717@server.gisp.dk> (raw)
Hi List,
I have some problems handling many requests to a tcp server in eCos 2.0.
I am using the code found in net/common/v2_0/tests/server_test.c (I don't
modify it at all)
I have no problems connecting to the server on that port. However, when I
continuosly send tcp requests to the eCos tcp server, reads the response,
and then closes the socket, the server always stops responding after 1132
requests has been handled.
Furthermore I tried running gdb remote and debugging the server. Then it
stop responding after 15 requests, and I was not able to figure out why.
Does anyone have an idea of what could causing this?
The hardware platform is i386, and I am using redboot.
--
Michael Birkmose
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-12-02 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 11:59 Michael Sig Birkmose [this message]
2003-12-02 12:53 ` Andrew Lunn
2003-12-02 13:03 ` sandeep
2003-12-02 15:07 ` Andrew Lunn
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=20031202131549.Y54717@server.gisp.dk \
--to=michael@gisp.dk \
--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).