HI,
I am maintaining an application which talks to another application via soap. When the calling application runs I tend to get time out errors which I need to handle but for some reason the calling application is not handling these two well (it needs to undo changes etc).
So in my test, I wanted to reproduce the time out error so I put a break point in the called application so the connect will fail.
However, my application does not fail with a connect time out error but an receive time out error. In other words, if I do not get data back after x seconds I get a time out, which I can configure in the calling application.
It appears that a TCP/IP connect has been done. Even though the called application has a break point that is hit, I would have expected all communication with the application to be frozen thereby giving a connection time out.
So my question is as I am missing some theory, what is happening under the hood? Is the TCP/IP connect done at the network layer which means that freezing my called application is pointless.
JD