|
7.3, but this process started back on 7.1.
We started running this process in 2016. We first saw this issue a
week ago Monday. Once the first error appeared, every subsequent call failed.
It did it again yesterday. Just like before, once the first error
appeared, every subsequent call failed. I was out of the office both
days, and I had ops bounce the Apache server. Both times that
immediately fixed the problem.
I can't replicate it inside or outside of HTTP.
Yes, the URL is a literal in the RPG code.
Eliminating the error would be ideal, but right now I'd just settle
for damage control (ie. when the first error happens, do something to
prevent the string of subsequent errors).
Thanks
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.