RE: Initiating SOAP Request from RPG Using Sockets

> From: Andrew Papada
>
> Just curious, you state that it only creates a JVM on the first call.
> Is this assuming that the RPG program will not be shut down after the
> call?  I believe that they are going to write a separate RPG program
> that would be called from the OMS each time it decides it is necessary
> to retrieve the desired info from the service.  In that scenario,
would
> only one JVM still be invoked?  I guess I'm thinking that each call to
> the RPG program would instantiate a new object from the prototyped
> class?  If it wouldn't invoke a new JVM in this case, I may be able to
> go back to them with this as a viable solution.

While there has been some revamping of the actual implementation from
release to release, the basic idea is that each job gets its own JVM,
and it can have only one.  You can manually start it with an API, or you
can let the RPG/Java interface start it for you.  In either case, once
the JVM is started, that is the JVM that will be used throughout the
job.

IIRC, that same JVM is even shared across activation groups.

A couple of caveats: if you manage to shut down the JVM, you cannot
start a new one.  The JVM is toast and the job cannot have another.  I'm
not sure why that is, but that's currently how it works (at least
V5R2+).  Also, if you create objects in your RPG calls (for example, you
invoke constructors to create new instances of objects), then it is your
responsibility to garbage collect them.  I'm pretty sure there are
examples of that in the archives.

Joe