Neil Could be that you have a portion of code which normally doesn't take a while to run but for some reason is taking longer than usual and hence the lock is timing out. You should be able to find out where the lock is timing out and examine what the code is doing, especially if its locking database access or access to some other third party component such as COM object. You can of course increase the timeout but better to determine why it is/was timing out.
HTH Kola > -----Original Message----- > From: Neil Middleton [mailto:[EMAIL PROTECTED] > Sent: 15 August 2006 08:59 > To: CF-Talk > Subject: "A timeout occurred while attempting to lock x" > > We had a server go sideways this morning repeatedly throwing the error "A > timeout occurred while attempting to lock x" where x is a named lock. > > We restarted CF which seemed to have no effect. Only a full hard reboot > seemed to fix the problem. The confusing part is that this only effected > one application on the server, no others (same instance of CF too). > > Does anyone have any ideas as to what the problem might have been? Could it > something more related to the JVM? > > -- > Neil Middleton > > Visit feed-squirrel.com > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:249810 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
