Re: Number of active CGI jobs -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

The HTTP server spawns a new CGI job when every other job in the pool is
otherwise occupied (processing requests). The maximum size of the pool of
active CGI jobs is configurable; defaults apply when not configured. CGI
jobs that crash can altogether crash the HTTP server under heavy load.

On Fri, Feb 11, 2022 at 5:27 AM Dave <dfx1@xxxxxxxxxxxxxx> wrote:

Hi,

My server configuration has no StartCGI or MaxCGIJobs directives. I
suppose I should need to have an idea how many concurrent http requests we
may have to deal with before setting these. During testing, I noticed that
a second CGI job was being spawned when the first one crashed. How does
that work? Is the second job spawned as soon as the first crashes or is
there some kind of delay in responding to the request that triggers this?

Thanks
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.