"Mike B." <mbrickman@radsol.co.uk> wrote in message
news:1170081720.386321.195270@a34g2000cwb.googlegroups.com...
> 1) Can anyone account for why threads/contexts get abandoned in an
in-
> active state.
You have not provided enough details to diagnose that. What does your
code actually look like? Which TIdScheduler component are you using?
How often are the clients connecting/disconnecting?
My guess would be that the clients with the hung threads are not
disconnecting from the server properly in the first place, so Indy
doesn't detect the closed sockets and thus cannot terminate the
threads immediately.
> 2) Is there a safe way of tidying up these threads.
Not really, aside from looping through the threads disconnecting the
sockets manually.
Gambit
