What do you mean by "concurrency", here? Are you trying to call
HTTPAPI in a multi-threaded environment? You almost never see people
use multi-threaded code in RPG, so this would be very bizarre. HTTPAPI
is not designed for multi-threaded access.
If you are running multiple copies of HTTPAPI in separate jobs or
activation groups, there is no problem.
However, you are running an 11 year out-of-date version of HTTPAPI. Who
knows what bugs have been fixed in the past 11 years? I certainly can't
remember everything that has happened in that time. Considering updating.
On 5/28/19 6:00 PM, Mike Jones wrote:
HTTPAPI Version 1.23 released 2008-04-24call
We're using the HTTP API plus internal web services and are occasionally
experiencing a concurrency issue, where the results of one web service
are getting mixed up with the results of a different web service call.course,
RPG <--> HTTP API <--> Java Web Service
Our RPG and Java teams don't think the problem is in their code (of
which I don't necessarily believe). But, they asked me to look into if
there have ever been concurrency issues in the HTTP API product by Scott
K. Has anyone seen any concurrency issues like that?
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate