Hello,

I'm trying to track down a situation with our proprietary
application server. We are running it on a Windows 2000
Advanced Server system. At any time, we have at least 50
clients connected to it. We are leaking Windows handles.
Despite analysing and sifting through our code several
times, we have been unable to find any problem with our
code (which is not to say that there isn't one) that
could constitute this leak. Is there any way that one can
find out what kinds of handles these are (file, socket,
etc) by using an API call ? Any insight would be greatly
appreciated.

Regards,

Mandar

There's a free download from sysinternals.com which lists
handles open by any particular process.

>-----Original Message-----
>Hello,
>
>I'm trying to track down a situation with our
proprietary
>application server. We are running it on a Windows 2000
>Advanced Server system. At any time, we have at least 50
>clients connected to it. We are leaking Windows handles.
>Despite analysing and sifting through our code several
>times, we have been unable to find any problem with our
>code (which is not to say that there isn't one) that
>could constitute this leak. Is there any way that one
can
>find out what kinds of handles these are (file, socket,
>etc) by using an API call ? Any insight would be greatly
>appreciated.
>
>Regards,
>
>Mandar
>.
>