RE: Starting JVM in RPG Before Making a Java Method Call

Hi Barbara,

I found that the RPG calling the Java method was not slow, but rather the
code within the method.  I am stumped.  Basically all I am doing is calling
a Web Service using the Axis API's.  The first time (for each 400 session)
the call is slow.  After the first call, everything is fast.  Once you
signoff and back on again, you get the same results.  The first Web Service
call is slow and the remaining calls are very quick.  I compiled/optimized
all the Axis jars.  I'm not sure what else to do.

Thanks,
Chad Cornelius, IIS
(720) 921-7835


-----Original Message-----
From: Barbara Morris [mailto:bmorris@xxxxxxxxxx] 
Sent: Tuesday, September 27, 2005 3:23 PM
To: java400-l@xxxxxxxxxxxx
Subject: Re: Starting JVM in RPG Before Making a Java Method Call

"cornelius, chad" wrote:
> 
> Barbara,
> 
> I did get the example to work from the link you provided.  However, the
> first call to a Java method still takes around 15+ seconds.  We are using
> JDK 1.4.  I am not sure if that's a problem or not since the JNI Module
> defines OS400_JVM_12.  Do your method calls perform quickly?
> 

Do you mean that after you manually started the JVM, then the first
method call after that took 15+ seconds but subsequent calls were
faster?  I would have expected the "start JVM" part to take 15+ seconds
and then all method calls to be relatively fast.

I don't think there is any way to speed up the starting of the JVM.

JDK 1.4 should be fine with OS400_JVM_12.  The Java invocation API
changed between JDK 1.1 and 1.2, but it's still the same as the 1.2 JDK
for all subsequent JDKs; by defining OS400_JVM_12 you are just saying
you are using the newer form of the invocation API.