HTTPAPI GET command "stuck" and causing data feed job to hang
Posted: Wed Jun 24, 2026 4:45 pm
We have an IBM i data feed job that uses the HTTPAPI http_url_get procedure to pull in data from a vendor server. This data feed job has been running fine for quite a while.
But recently, the job has been hanging indefinitely on the http_url_get procedure even though the timeout specified is 240 seconds. The last thing the job is doing when it hangs is this:
Program HTTPAPIR4 Statement 4844 Procedure COMMSSL_READ
Program QSOSSLSR Statement 11 Procedure gsk_secure_soc_read
I need to end and restart our data feed job when this happens. It then seems to run for an hour or so pulling in data just fine.. then it locks up again with the same symptoms.
I looked at our XML files that we're pulling data into (I presume?) and there only 160KB. So I don't think there is a data size issue going on...But it looks like there is data in them, but it's incomplete...like it stopped in mid action....
I'm a bit new to the web API interfaces, so I'm not sure where to look on the IBM i next to see if there are any errors or issues with this process?
Any thoughts on this? It seems to me that there's something that's changed with the network connection between our vendor and our IBM i? Or do you think this could be an issue with the data we are retrieving that's causing the http_url_get procedure grief?
Any insight would be greatly appreciated.
Thanks!
JKING
But recently, the job has been hanging indefinitely on the http_url_get procedure even though the timeout specified is 240 seconds. The last thing the job is doing when it hangs is this:
Program HTTPAPIR4 Statement 4844 Procedure COMMSSL_READ
Program QSOSSLSR Statement 11 Procedure gsk_secure_soc_read
I need to end and restart our data feed job when this happens. It then seems to run for an hour or so pulling in data just fine.. then it locks up again with the same symptoms.
I looked at our XML files that we're pulling data into (I presume?) and there only 160KB. So I don't think there is a data size issue going on...But it looks like there is data in them, but it's incomplete...like it stopped in mid action....
I'm a bit new to the web API interfaces, so I'm not sure where to look on the IBM i next to see if there are any errors or issues with this process?
Any thoughts on this? It seems to me that there's something that's changed with the network connection between our vendor and our IBM i? Or do you think this could be an issue with the data we are retrieving that's causing the http_url_get procedure grief?
Any insight would be greatly appreciated.
Thanks!
JKING