I saw some references that STOP-AFTER doesn't work for timing out socket connection. Is this true also for the webservice CONNECT statement?
I beleive so.
This is my finding;
If the STOP-AFTER is used inside a .p wrapping the CONNECT call, the application either hangs or just shutdown.
EX.
Inside procedure.p
DO STOP-AFTER
CONNECT
END.
If I wrap the .p itself that contains the CONNECT call with STOP-AFTER, it seems to work fine.
EX.
DO STOP-AFTER
RUN procedure.p. /* contains CONNECT*/
END.
What do you think is happening? Can I correctly assume that the second sample is acceptable/reliable, or is it just a fluke that it works as expected in my second sample program?
* jmls goes to check...
On 5 Oct 2012 21:10, "Joseph Querijero"