Re: MCH74A5 - The Java Virtual Machine has ended

From: Scott Klement
On my system, anyway, if a job fails, Apache starts a new one to
take it's place.

Perhaps, up to a configuration limit.

And since you don't get the same job on every call, you
can't rely on anything to have previously been set up in the job,
anyway.

Right. That's the way CGI works. But I'm not sure how that might apply in this case. Maybe Peter can answer if the RPG-Java process relies on an initialization step or other type of state being established before handling HTML-PDF conversion requests. If so, that would be a good reason to communicate over a data queue.

So why would it maroon anything?

There have been quite a few reported cases where an errant CGI program eventually locks up an entire HTTP server. The multi-threaded server job dispatches requests to CGI server jobs - and waits. The next request for the CGI program goes to the next available CGI process - and waits. Eventually a thread configuration limit is reached, and no additional CGI server jobs are started, and the HTTP server job locks up. That seems to be the usual scenario, however it seems that there have also been cases reported where an errant CGI process locks up the HTTP server to the degree that ENDJOB is the only option.

Nathan.