×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Tue, Sep 18, 2018 at 1:37 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:
Unless there's something left out of the picture here, I'll reiterate that
the Apache server shouldn't have anything to do with HTTPAPI.
Brad,
Justin hasn't really explained it, but he's evidently making HTTPAPI calls
from an IBM i CGI program, which itself also responds to HTTP requests. Web
applications and web-service servers (CGI programs) can be web-service
clients too.
The problem here appears to be that the error in the CGI program
destabilizes the HTTP server. So far, the fix is to restart the HTTP
server, which is obviously is NOT GOOD.
One way to eliminate the problem would be to make the HTTPAPI calls from a
separate job, which communicates with the CGI program via data queues. That
would at least keep the HTTP server from becoming destabilized. Ultimately,
he needs to add error handling to the program that's making HTTPAPI calls.
Nathan.
As an Amazon Associate we earn from qualifying purchases.