Fwd: StartCGI bug?

I restarted the server and sent a request to the base URL so that only
index.html was returned in order to avoid calling any CGI program that I
know of. The result is the same, 2 groups of 2 CGI jobs but now no entries
in the logs for any of them.

CgiInitialUrl is not used. Reading up on that directive and PGM-QZSRHTTP, I
discovered HotBackup. As this is on by default maybe this is normal
behaviour (2 primary PGM-QZSRHTTP jobs) ? Am I seeing on server startup the
1st group of CGI jobs as per StartCGI and at after the first request I'm
actually looking at the backups waiting to take over if my first primary
job crashes? After reading about CgiInitialUrl, I’m wondering if the lag
I’m noticing is actually because of an activation group being initiated on
the first call as described in the manual for CgiInitialUrl.






From: *Nathan Andelin* <nandelin@xxxxxxxxx>
Date: Mon, 7 Mar 2022, 20:29
Subject: Re: [WEB400] StartCGI bug?
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>



I haven't ever run into a case where another set of CGI jobs are started,
except when existing jobs are "busy".

By chance, are you also using CgiInitialUrl in combination with StartCGI?
Could it be that an initially loaded program is running, which hasn't
returned a result?


On Sun, Mar 6, 2022 at 11:39 AM Dave <dfx1@xxxxxxxxxxxxxx> wrote:

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.

--
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.