Maybe I missed it, but which version of http_post are you using ?

In today's world if I'm using RPG I tend to the QSYS2 version of the http functions vs the SYSTOOLS versions.

Might be worth trying the newer ones if you're using SYSTOOLS versions.

Also testing with CURL, Python or something else might be interesting to see if you see similar results.

At least then you can truly narrow it to network issues vs particular language version API issues.

My two cents.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx

----------------------------------------------------------------------

message: 1
date: Mon, 23 Feb 2026 12:26:02 -0600
from: Justin Taylor <jtaylor.0ab@xxxxxxxxx>
subject: Re: does anyone have any real understanding of this msg...

What's the SQLSTATE?

On Mon, Feb 23, 2026 at 10:55?AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

when invoking an http_post...

{"program":"xxxxxxxxx","service":"xxxxxxxxxx","error":"AXISC ERROR :
HTTPTransportException: Cannot initialize a channel to the remote
end.\nFailed to establish SSL connection to server, the operation
gsk_secure_soc_init() failed.\nGSKit Error is 415 - Peer not
recognized or badly formatted message received."}

we have many of these outbound http_posts which have successful
responses, behaving as they should, then out of nowhere we start
getting these and due to the volume of requests, gating starts
occurring and our IBM i env begins deteriorating pretty rapidly.

Then all the sudden, they begin working again.

We can only conclude it is an issue with the endpoint, but we can't
nail down exactly what is going on with that. The guys behind the
endpoint say they see no errors and it's our issue.


tia

Jay





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-2026 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.