Original Message-
> From: Ryan Guill [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 23, 2006 11:09 AM
> To: CF-Talk
> Subject: Re: weird locking error
>
> To track what locks are active, you could put code inside of the lock
> that sets an application variable and then
ent to Adobe
> for a hotfix but the one we received broke our system even more (not that I'm
> complaining, they did their best).
>
> > -Original Message-
> > From: Russ [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, March 22, 2006 3:10 PM
> > To: CF-Tal
n went to Adobe
for a hotfix but the one we received broke our system even more (not that I'm
complaining, they did their best).
> -Original Message-
> From: Russ [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 22, 2006 3:10 PM
> To: CF-Talk
> Subject: weird locking
Is there some bug in CF7 that doesn't release locks? We have a lock on a
page that works fine, but while we were QAing it, we started running into
exceptions with the time out. The timeout is set to 60 seconds, and it
works again if I rename the lock, and also works after server restart.
Is
"Steven
Dworman" To: CF-Talk <[EMAIL PROTECTED]>
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 31, 2001 8:36 AM
To: CF-Talk
Subject: locking error
Can someone explain this error to me? I took out the locks in the
application.cfm file when I got this error message.
Unable to acquire lock for single threaded sessions within timeout period
Can someone explain this error to me? I took out the locks in the
application.cfm file when I got this error message.
Unable to acquire lock for single threaded sessions within timeout period.
Please raise the request timeout limit to lengthen the time available to
acquire the lock.
The er
7 matches
Mail list logo
