From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28708] run-debuginfod-webapi-concurrency.sh seems to be flaky
Date: Sun, 24 Apr 2022 10:23:56 +0000 [thread overview]
Message-ID: <bug-28708-10460-OcDkXkOcQO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28708-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28708
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #14 from Mark Wielaard <mark at klomp dot org> ---
commit 3bcf887340fd47d0d8a3671cc45abe2989d1fd6c
Author: Mark Wielaard <mark@klomp.org>
Date: Sun Apr 24 12:16:58 2022 +0200
debuginfod: Use MHD_USE_ITC in MHD_start_daemon flags
This prevents the "Server reached connection limit. Closing inbound
connection." issue we have been seeing in the
run-debuginfod-webapi-concurrency.sh testcase. From the manual:
If the connection limit is reached, MHD’s behavior depends a bit
on other options. If MHD_USE_ITC was given, MHD will stop
accepting connections on the listen socket. This will cause the
operating system to queue connections (up to the listen() limit)
above the connection limit. Those connections will be held until
MHD is done processing at least one of the active connections. If
MHD_USE_ITC is not set, then MHD will continue to accept() and
immediately close() these connections.
https://sourceware.org/bugzilla/show_bug.cgi?id=28708
Signed-off-by: Mark Wielaard <mark@klomp.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-04-24 10:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 1:02 [Bug debuginfod/28708] New: " evvers at ya dot ru
2021-12-17 1:25 ` [Bug debuginfod/28708] " evvers at ya dot ru
2021-12-17 1:53 ` fche at redhat dot com
2021-12-17 2:30 ` evvers at ya dot ru
2021-12-17 8:31 ` mark at klomp dot org
2021-12-17 18:48 ` fche at redhat dot com
2021-12-17 18:48 ` fche at redhat dot com
2021-12-17 18:49 ` fche at redhat dot com
2021-12-19 22:06 ` evvers at ya dot ru
2021-12-19 22:47 ` fche at redhat dot com
2021-12-20 17:17 ` mark at klomp dot org
2021-12-20 23:21 ` evvers at ya dot ru
2022-04-03 0:43 ` fche at redhat dot com
2022-04-04 2:27 ` evvers at ya dot ru
2022-04-05 14:09 ` mark at klomp dot org
2022-04-24 10:23 ` mark at klomp dot org [this message]
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=bug-28708-10460-OcDkXkOcQO@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/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).