It means that whatever value you had for the timeout attribute in your
cflock tag was too short. You received the error message because you had
throwontimeout="yes".
Instead of removing the locks, either increase the timeout value or
consider moving from a scope lock to a name lock so you can lock only what
you have to, rather than locking all the variables of an entire class
across all applications on the server.
|-----------------------+-------------------------------------------------|
|Eric A. Laney |One's real life is often the life that one does |
|Systems Engineer |not lead. |
|LAN Optimization Team | |
|Voice: 813.978.4404 | |
|Pager: 888.985.8519 | |
|-----------------------+-------------------------------------------------|
"Steven
Dworman" To: CF-Talk <[EMAIL PROTECTED]>
<dwormans@msu cc:
.edu> Subject: locking error
07/31/2001
11:35 AM
Please
respond to
cf-talk
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 error occurred while processing an element with a general identifier of
(CFAPPLICATION), occupying document position (1:1) to (4:58) in the
template
file
/data1/entdocs/devwww.vzncontract.com/cfm/vzncontract/vzn/Application.cfm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
- locking error Steven Dworman
- RE: locking error Mike Brunt
- eric . laney
