Yeah, I though it was working Monday...

But Tuesday we were seeing issues with an invalid SSL handles...

We did end up using activation groups to solve the issue.


On Tue, Jan 22, 2019 at 8:46 PM Scott Klement <web400@xxxxxxxxxxxxxxxx>

Consider running them in separate activation groups -- then each will
have its own copy of HTTPAPI.

If you can't do that, then the problem will be any global setting will
be kept the same. You've found the exit points, but other things like
CCSIDs, logs, http_auth settings, etc will be kept. This isn't a problem
if you set them all before each request (or disable the setting) -- then
it will work fine, you just have to be careful to avoid settings being
left over from the last request.

On 1/22/19 12:08 AM, Charles Wilt wrote:
- PGMA using HTTP API to contact ServiceA
- ProcB in a service program which calls ServiceB

If PGMA has an open to connection to ServiceA, but between request calls
ProcB, is that asking for trouble?

I saw an issue with http_xproc(HTTP_POINT_ADDL_HEADER), since both PGMA
ProcB were setting it, I had to reset it in PGMA after my call to ProcB.

Is there anything else I should be concerned about? At first glance,
not using any of the other http exit points. I can see where debug
settings might be an issue.

Thank you!

Scott Klement

This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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.