Re: First CGI request to webserver times out.

[Scott Klement <web400@xxxxxxxxxxxxxxxx>]

Hello Rune,

Take a look at the CgiInitialUrl Apache directive.  It lets you specify 
a CGI program to call immediately when Apache starts jobs to run CGI 
programs in.  This gives the program a chance to initialize (in your 
case, this would give you the opportunity to start the JVM)

An alternative to CgiInitialUrl is to start up a batch job to handle the 
Java part of your workload.  Your CGI program can use a data queue to 
communicate with the batch job -- so if the batch job stays active, it 
doesn't have to re-load the JVM.

Both approaches work -- but the CgiInitialUrl directive is a bit closer 
to what you've asked for.

Rune Kaus wrote:
> Hi gurus.
>
> I'm a fairly experienced java and rpg programmer but this is my first 
> attempt on an RPG CGI-program that calls java.
>
> Env:
>     i5/OS V5R4
>     Java 1.5
>     ILE RPG
>     IBM Httpserver powered by Apache
>
> One cgi rpg-program has been running for many years, but was recently 
> extended with a few java classes and methods
>
> This application works and runs like clockwork except:
>
> My problem is that the *first* request to the cgi-program, after the 
> server is restarted, where the javapart is involved seems to time out 
> and return an error. Starting the jvm is the timeconsumer it seems, 
> because subsequent requests have very fast response times.
>
> Is there a way to avoid the jvm startup cost when a user is involved?
> Can the jvm be started up front? Seems like the server cgi-jobs does not 
> start until there is a request for the cgi-program.
> Or maybe a timeoutvalue can be changed to enable the server to return a 
> normal response?
>
> Any hints, comments and pointers are greatly appreciated.
>
> Regards Rune