[THIN] Re: CriticalSectionTimeout
- From: "Andrew Wood" <andrew.wood@xxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Sun, 9 Dec 2007 20:26:18 -0000
Joe,
I found that out as well.
What I'd like to know is not what it does per se - but if anyone has ever
come across the need to change it. From what I've read I'd suggest that
someone has changed it because they couldn't get code fixed for one reason
or another .
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Joe Shonk
Sent: 08 December 2007 04:22
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: CriticalSectionTimeout
Tim could probably expand on this, but based on a little light reading on a
Friday Night you could respond like this:
Your applications utilizes critical sections and you don't want wait 30 days
for the system to resolve deadlocks.
or
The value of the CriticalSectionTimeout is not used unless the value is
equal to or under 3600 (1 hour) secs.
Joe
On Dec 7, 2007 5:33 PM, Andrew Wood < andrew.wood@xxxxxxxxxxxxxxxx
<mailto:andrew.wood@xxxxxxxxxxxxxxxx> > wrote:
Got asked this today:
"Ha ve you ever changed, or had a reason to change or know of a reason why
you would change HKLM\System\CurrentControlSet\Control\Session
Manager\CriticalSectionTimeout " from it's default value of 30 days?"
And the only answer I could come up with was 'code that doesn 't handle
deadlocks properly' - anyone else got a bright idea?
Tia.
Andrew
Gilwood CS Ltd
Registered Office : 197 Leechmere Ro ad, Sunderland, UK, SR2 9DL. No.
6099397 England
Other related posts:
