Re: How to monitor for CGI program crashing

I would say the "right way" is open to interpretation.

Stop the program from halting.
Capture any error.
Generate an email with the error and log information and have the application email the entire team when an error occurs.

Allow the CGI program to complete with an error or send back a known HTTP code to denote an error has occurred.

But #1 here is "Stop the program from halting."
There are many methods to do that, and most would depend on what language the CGI program is coded in.


--
Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

From: WEB400 <web400-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dave
Sent: Friday, October 7, 2022 7:10 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>
Subject: [WEB400] How to monitor for CGI program crashing


I've just found out that when this happens, we rely on one member of the

team to occasionally check the message queue QSYSOPR. This poses a problem,

particularly when the said team member is asleep, for example. I was

horrified yesterday to see all the CGI jobs on one server blocked by a

program in *MSGW condition in the first JOB.

I am currently working on an application that reuses part of the code and

don't want to fall into this trap.

What's the right way to alert the team when this happens?



Thanks

--