RE: Java->RPG, *SERIALIZE required?

Multiple JVM threads would be calling the same RPG procedure concurrently, which would cause a bottleneck since the RPG would be single-threaded.

The RPG code is already available as a webservice, it just seems silly for a native IBMi job to have to call a local webservice to run an RPG program. Que sera, sera!

Thanks guys :)



-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Friday, March 06, 2020 12:26 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Java->RPG, *SERIALIZE required?

Because it's multi-threaded, and a single-threaded bottleneck would be
undesirable.

Now I'm curious about what you might be comparing thread(*serialize) to? I assume you understand that calling Java methods must also be serialized in muti-threaded Java processes. That's just normal practice within multi-threaded Jobs. The fact that RPG code might be single-threaded has nothing to do with it.

An alternative would be to communication between a pool of Java threads and a pool of RPG servers via data queues or some other form of inter-process communication.