>I know this is probably not what you want to hear but I'd guess that you >have CF5 or below code there... We *used* to duplicate in the same way you >did when we originally migrated to 6.1 but given that the locking issues are >far less of an issue on CF6 and above, it is probably save to say you will >see a major improvement in performance if you remove the duplicate and do a >search/replace on your entire project changing Request.AppGlobal. to >Application. >
Thanks for the suggestion. Yes, in this case, I am working on convincing the product owner that locking is unnecessary in most "read" situations and that it isn't necessary, but this is a huge production level application and we need a fix to the actual problem we are currently having. I would agree that locking in most cases is unnecessary unless you are writing to an app variable in a situation where it could be modified by multiple users, but in this case, I need to find out why the service is restarting and telling him that we need to take out all the locking and that will solve the problem -- he won't buy it, especially since it has worked fine for 2 years like that. What I need to know is has anyone else experienced such an issue and, if so, how was it resolved (other than search and replace)? Thanks! Dave ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:256974 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
