On Sun, Nov 28, 2010 at 4:37 PM, Russ Michaels <[email protected]> wrote: > > use the stack trace to try and determine the cause, also you should the JDBC > wrapper on your DSN so that you can use the JDBC diagnostics as well.
Yup, I did that, I know which query was run in each case, and they are queries that get run all the time... on pages that get accessed a lot. The queries that were frozen are queries that have probably run thousands of times since then. > The most likely cause is simply that cf did not get any response back form > the database, if the request is still open then you can use some process > monitoring on the sql server to see what it is doing. Yeah, that's what I'm thinking, that CF didn't get a response from SQL Server... on SQL 2005, there is an "Activity Monitor" in the enterprise mgmt console but that might be an enterprise only feature, and we've got SQL Server 2008 Standard ... I'll have to hit up google to see if there are any other methods of getting what the activity monitor shows in sql server... Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:339562 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
