|
Mike.
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.
-SK
On 5/28/19 6:00 PM, Mike Jones wrote:
HTTPAPI Version 1.23 released 2008-04-24call
OS/400 V7R3M0
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?
Mike
--
Scott Klement
http://www.scottklement.com
--
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,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.