Manage Locking Variables

Use the Locking page to specify locking settings that protect data:

  1. Click Server>Locking in the ColdFusion Administrator navigation frame. The Locking page appears.

  2. The Single Threaded Sessions option is disabled at installation; decide whether to use single threaded sessions. Single threading means that all requests from the same session occur sequentially. Each request waits for all previous requests to finish before proceeding, thereby preventing multiple requests from simultaneously accessing shared data.  

  3. Specify variable scope lock settings by clicking the appropriate option button. Each scope (server, application, and session) has three possible settings, as described in the following table:

 

Option

Description

Default

No automatic checking or locking

If you select this option, no automatic checking or locking occurs. The developer must protect variables with the cflock tag. If variables are not locked, data corruption can result and server instability can occur.

Yes

Full checking

This option causes ColdFusion to automatically check all shared variable scope access to ensure that it is properly locked. If any read or write of data in one of the scopes occurs outside of the scope of a cflock, an error occurs.

 

Note:  This form of lock checking should be applied only to applications that use the scope attribute of the cflock tag to specify locks, not the name. If you specify the name attribute, ColdFusion responds with an error on any variable accessed within the locked block if full checking is applied on the scope of the variable.

No

Automatic read locking

ColdFusion checks whether shared variable scope writes are locked and automatically locks shared variable scope reads. If ColdFusion encounters shared variable scope writes that are not locked, an error occurs.

No

 

  1. Click Submit Changes to save your settings.

Related topics