When running a procedure on an Appserver and there is a network disconnect during this time, the calling procedure could end up waiting forever for a response (OE 11.3.3 on RHEL 6, also reproduced on WIN).
So I've added a -clientConnectTimeout parameter to the connection string and wrapped the appserver call inside a DO STOP-AFTER section. I've used clientConnectTimeout of 60000ms and STOP-AFTER of 60s.
Now when I break the network connection during a call the STOP-AFTER kicks in and I can trap the timeout after roughly 60 seconds. This is good news.
But what's interesting is that if the appserver call itself exceeds 60s without any network interruption (in my case I've paused for 80s), I only get the STOP condition when the appserver completes (after 80s). So it seems it's still waiting for the appserver call to complete.
Ideally I would not like to raise any errors if the appserver did complete - only in case of a network connection I would like to raise an error.
Anyone knows how to deal with this?