Why "WaitForSingleObject" need more time on "windows 2003 server R2" than "windows 2003 server"  (all with SP2)?
For example:Process A create Process B and exchange messages between them.Once Process A found that Process B is gone, Process A will call "WaitForSingleObject" on Process B.The details about the function "WaitForSingleObject" is as follows: WaitForSingleObject(HANDLE hHandle, DWORD dwMilliseconds)If I set the dwMilliseconds to 0, On "windows 2003 server", "WaitForSingleObject" will return "WAIT_OBJECT_0" -- succeed.But on "windows 2003 server R2", "WaitForSingleObject" will return "WAIT_TIMEOUT" -- timeout.If I set the dwMilliseconds to 1000 on "2003 server R2", "WaitForSingleObject" will return "WAIT_OBJECT_0" too -- succeed.Some system behavior must have been changed between "2003 server" and "2003 server R2", but I can't find any official documents about this.Can anyone tell me something about this?Any suggestion is appreciated.Thanks very much.
March 14th, 2009 11:19am

Hi, According to the description, the issue seems to be related to development/coding. As we are mainly focus on the general question about Windows Server, for accurate answer to the question, it is recommend you to initial a new thread in the MSDN forum to get further support. MSDN forumhttp://social.msdn.microsoft.com/Forums/en-US/categories/ I have included a document for your reference WaitForSingleObject Functionhttp://msdn.microsoft.com/en-us/library/ms687032(VS.85).aspx Hope the issue will be resolved soon. This posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2009 12:58pm

Thanks very much.I will try it.
March 16th, 2009 1:10pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics