Thanks Dirk, I was expecting something like that ... that it relies on API calls :(
-------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Sent: 26 August 2008 13:16 To: Servers Alive Discussion List Subject: RE: [SA-list] Perfmon check Some of the checks are threaded, not all. And the perfmon check is NOT threaded. The perfmon checks does an API call towards the (remote)system and some API calls (the perfomn calls are a nice example of those) do NOT have a timeout setting and can hang an application, this is how the APIs (part of the OS) are. What can we do about it? For the moment nothing. In the future when more checks will be threaded, we will probably also thread the perfmon checks and then a "thread" could hang for a longer time, but this should not effect the rest of the app. Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr Bohac Sent: Tuesday, August 26, 2008 11:01 AM To: Servers Alive Discussion List Subject: [SA-list] Perfmon check Hi Dirk, I found a small issue in the NT perfmon check. We do have a server which is quite busy and his response particularly to perfmon test is very slow. Sometimes it might take a minute or two to get a response (even when you start perfmon app and connects to the server you get a delay, so the problem is not the SA). The problem is that it hangs SA for quiet a long time. The UI is unresponsive and no other checks are being processed. The timeout value is by default set to 10 but it seems the check doesn't reflect the value. I believed that all the default checks are multi-threaded but apparently not. Is there a way how to fix it or get it improved? Thanks, Petr -------------------------------------------------------------------------------- This e-mail including any attachment is intended only for the recipient(s) named. It may contain confidential information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender and delete the e-mail from your system. The sender does not accept any liability for errors or omissions in the content of this message or for viruses, or any damage due to the e-mail. The recipient is advised to have appropriate virus check software. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. -------------------------------------------------------------------------------- This e-mail including any attachment is intended only for the recipient(s) named. It may contain confidential information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender and delete the e-mail from your system. The sender does not accept any liability for errors or omissions in the content of this message or for viruses, or any damage due to the e-mail. The recipient is advised to have appropriate virus check software. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
