That article is quite old (2005).
> On "TfrmServer.httpServerCommandGet" I am doing the page processing.
That code is not thread-safe. And much of its logic is redundant as well,
as it is duplicating logic that TIdHTTPServer natively implements
internally.
> At one instance, I need to run an external function (which takes
> 5-7 secs) to do some database processing and I have to show
> the corresponding error page.
>
> During this time, it comes up with an access violation with the
> "EIdSocketError Socket Error # 10054 Connection reset by peer"
The only way that error can occur is if the socket is being disconnected
abnormally on the client side while waiting for the server's reply. Changes
are, the client has a timeout implemented on its end, and is not closing its
socket endpoint properly.
> The call trace looks like this
You did not say which version of Indy 9 you are using. If you ave not
already done so, make sure you are using the latest Indy 9.0.50 snapshot,
and then see if the problem continues.
Gambit
