Re: StartCGI bug?

If I code StartCGI 2, at server startup I'm seeing :

PGM-QZHBMAIN

PGM-QZSRLOG

PGM-QZSRLOG

PGM-QZSRHTTP

PGM-QZSRCGI

PGM-QZSRCGI


After the first http request is made I'm seeing :

PGM-QZHBMAIN

PGM-QZSRLOG

PGM-QZSRLOG

PGM-QZSRHTTP

PGM-QZSRCGI

PGM-QZSRCGI

PGM-QZSRHTTP

PGM-QZSRCGI

PGM-QZSRCGI



By « pool » I was thinking of a group

PGM-QZSRHTTP

PGM-QZSRCGI

PGM-QZSRCGI


I'm presuming the first request is slow because of the 2nd group of jobs
that get activated. But why does it get activated? The whole point of using
StartCGI is to avoid waiting for a new job to be created.



On Thu, 3 Mar 2022 at 00:30, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I'm not sure if concurrent requests are made asynchronously or not.

If logging is configured for your HTTP server instance, you can check the
timestamp of each request to see whether multiple requests are made in say
< 1 second. The HTTP server automatically starts new CGI Jobs under load,
whenever a new one is needed.

StartCGI 5 is indicated and there are 2 pools of 5 CGI jobs each time.


By "2 pools", I assume you're referring to 2 HTTP Server Instances.

When the server is started
there is 1 pool of 5 jobs, then after the first request there are 2 pools
of 5.

That doesn't make sense to me.

why is the first request taking so long

I would guess some sort of resource contention during activation.

why do I have
twice as many jobs running afterwards as indicated in StartCGI?

Again, that doesn't make sense to me. You seem to be saying that there are
2 pools of CGI Jobs for a single HTTP Server instance. What does pool mean,
for you?
--
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.