Adam,
Why does it fix it? Why do we see this in our application only when using
Indy 10? Why is this such a mystery?
Mark
"Adam Lister" <adam@SPAMLESS.tombola.com> wrote in message
news:442923e6$1@newsgroups.borland.com...
> Mark D. Lincoln wrote:
>> Ciaran,
>>
>> Here is the problem with using the try...except to work around the
>> problem, it does not solve the root problem in Indy 10. It simple deals
>> with the simptom. In addition, once the error appears, the communication
>> between the client and server fails everytime, so the try..except would
>> simply try forever. What we really would like to know is why production
>> code that has run for four (4) years 24/7/365 on our servers with Indy 8
>> and then Indy 9 now does not work with Indy 10? What changed in Indy 10
>> that broke our system?
>>
>> As for the client code, we are simply using the Post() method of the
>> TIdHTTP class passing the URL, the request data stream, and a stream to
>> be filled with the response data.
>>
>> Mark
>>
>
> Try issuing a DisconnectSocket command in the exception handling code. I
> get 10054 exceptions from time to time with Indy 9, I "think" its due to a
> keep-alive session dying because its not been used for a few minutes, it
> seems especially prone to doing it if the last http command failed for any
> reason.
>
> Either way, DisconnectSocket seems to fix it for me
