http://www.parmiter.com/microsoft/windows-2003/2009/07/RP607 Virtualisation blog and Knowledge Base Thu, 24 Nov 2011 01:37:52 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://www.parmiter.com/microsoft/windows-2003/2009/07/RP607/comment-page-1#comment-144 laca Wed, 19 Jan 2011 22:40:19 +0000 http://www.parmiter.com/?p=607#comment-144 Hi! The CriticalSectionTimeout value is handled by the Windows kernel32.dll, and is related to multi-threading. A CriticalSection is a section, when a multi-threaded program's two or more threads try to read and write a value simultaneously. So if two threads try to increment a value by 1, the result should be 2, if a CriticalSection given to the object or code segment, if not, the result will be 1, because the two threads read the same base zero value, and they give the holder (memory block) the same incremented value. So, a CriticalSection makes the other threads wait until the one finishes the section. The CriticalSectionTimeout is the minimum value in seconds a thread should wait. 2592000 seconds is 30 days, but this should not happen, except in a DeadLock. Hi!
The CriticalSectionTimeout value is handled by the Windows kernel32.dll, and is related to multi-threading. A CriticalSection is a section, when a multi-threaded program’s two or more threads try to read and write a value simultaneously. So if two threads try to increment a value by 1, the result should be 2, if a CriticalSection given to the object or code segment, if not, the result will be 1, because the two threads read the same base zero value, and they give the holder (memory block) the same incremented value. So, a CriticalSection makes the other threads wait until the one finishes the section. The CriticalSectionTimeout is the minimum value in seconds a thread should wait. 2592000 seconds is 30 days, but this should not happen, except in a DeadLock.

]]>