Newsgroups : Borland : borland.public.delphi.internet.winsock : 2007 Jan : Re: CPU at 100% causing ClientSocket disconnect

www.cryer.info
Managed Newsgroup Archive

Re: CPU at 100% causing ClientSocket disconnect

Subject:Re: CPU at 100% causing ClientSocket disconnect
Posted by:"Angela Bodnar" (angela.bodn..@noris.org)
Date:24 Jan 2007 09:09:27

I really didn't think you wanted to see thousands of lines of
code from me.  I was just trying to find out if there was a
known problem of this type.  I'm not even sure if the CPU is
at 100% everytime.  It was just noticed by the operator.
Sometimes the program will recover itself and reconnect after
sensing a disconnect.  Sometimes it can not recover and this
is ususally accompanied with a socket error 10053 or 10054.

What could possibly cause "overloading the socket" or
"blowing up a thread"?

Thanks.


"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>
>"Angela Bodnar" <angelabodnar@yahoo.com> wrote in message
>news:45af92e7$1@newsgroups.borland.com...
>
>> Thought I would try again since I haven't gotten any responses.
>
>You didn't really provide very many details the first time around, and
>you just repeated what you said without adding anything new to it.
>
>It would help if you would actually show your code.  You are probably
>overloading the socket, or blowing up a thread, or something like
>that.  Especially since you are seeing 100% CPU usage.  That in itself
>a usually a good indicator of a runaway thread.
>
>
>Gambit

Replies:

In response to:

www.cryer.info
Managed Newsgroup Archive