Hi all,

We recently upgraded our test server from CFMX 6.1 to ColdFusion 8, which 
causes our application much problems.
Because of the nature of our application and the way it is build, we use 
cflockextensively.
It seems that ColdFusion 8 has some serious issues with CFLOCK. After the 
upgrade, we found requests to be blocked for no obvious reason, while the CF 
monitor always shows  that the process is waiting for a lock (cflock is the 
final element in the stack trace).
We are using nested locks, but there are no deadlocks (believe me, I checked). 
Anyways, the CF documentation says that a deadlock would end when a timeout is 
reached. I'm now looking at a request that has been blocked for over 3 days 
(lock timeout = 30 seconds).

Here's the stack trace of the request:

**************************************
/opt/bea/wls_sp6/user_projects/domains/domaineistc/extend7010/stage/cfusion-ear/cfusion-war/eistc/components/SharedDirectoryListing.cfc
 cflock
at 
/opt/bea/wls_sp6/user_projects/domains/domaineistc/extend7010/stage/cfusion-ear/cfusion-war/eistc/components/SharedDirectoryListing.cfc
 getNextItem() : 138
at 
/opt/bea/wls_sp6/user_projects/domains/domaineistc/extend7010/stage/cfusion-ear/cfusion-war/eistc/components/SharedDirectoryListing.cfc
 check() : 116
at 
/opt/bea/wls_sp6/user_projects/domains/domaineistc/extend7010/stage/cfusion-ear/cfusion-war/eistc/tasks/archiving/setExpirydates.cfm
 cflock : 51
at 
/opt/bea/wls_sp6/user_projects/domains/domaineistc/extend7010/stage/cfusion-ear/cfusion-war/eistc/tasks/archiving/setExpirydates.cfm
  : 3
at 
/opt/bea/wls_sp6/user_projects/domains/domaineistc/extend7010/stage/cfusion-ear/cfusion-war/eistc/tasks/archiving/setExpirydates.cfm
 
**************************************

This is the only active request. No other requests are running. When I start a 
new request that waits for the same lock, it waits for the lock for 30 seconds 
and then times out, which leads me to believe that the long running request has 
obtained the lock.

This code worked without any issues on CFMX6, so there has to be something 
different in the way CF8 handles the locks.

Is there anybody out there that had similar issues after upgrading to CF8?

Is there a way to see all active locks on an application? The CF monitor does 
not seem to be able to give me the information I need to solve this issue.

Any help would be much appreciated!

Thank you,
Wim
Belgium 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to 
date
Get the Free Trial
http://ad.doubleclick.net/clk;192386516;25150098;k

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:305151
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to