SqlDependency.OnChange callback timing

January 4th, 2008

I had reviewed the way SqlDependency works several times in this blog, but the implementation of this feature will probably continue to surprise me for a long time. After reading about numerous reports of ERRORLOG files getting filled with messages like:

The query notification dialog on conversation handle '{5925E62A-A3BA-DC11-9E8E-000C293EC5A4}.'closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8470</Code><Description>Remote service has been dropped.</Description></Error>'.

I decided to take a closer look. The immediate cause of this error is quite clear, is it because the target service of a Query Notification subscription was dropped. I have covered the system error 8470 and others in my earlier post Resending messages. But of course, the real question is why is this happening? Is there some coding error on the part of the application developer and some way to avoid this problem? Is there some configuration issue?

My usual answer to people complaining about this problem was that they are calling SqlDependency.Stop method too often, thus causing the error. An application should call SqlDependency.Start once when it starts up and SqlDependency.Stop once when it shuts down. Calling it more often would typically be a coding error and the problem can easily be fixed by moving the code that invokes this method into a proper place, perhaps hooking into AppDomain.CurrentDomain.DomainUnload event.

However, it turns out that this is not always the cause. Lets look at how does SqlDependency wait for notifications. Our trusty friend the SQL Profiler reveals the query submitted by the SqlDependency background thread that waits for notifications:

This query will start a conversation timer with a timeout of 2 minutes (120 seconds) and then post a WAITFOR(RECEIVE…) with a timeout of 1 minute (60000 milliseconds). The idea here is that if the application exits abruptly the conversation timer will fire and this will cause the activated procedure attached to the queue to run and this in turn will cleanup the SqlDependency temporary infrastructure (the procedure itself, the service and the queue). Normally the application will not disconnect abruptly so the WAITFOR (RECEIVE) will timeout first after one minute causing the SqlDependency to post back the same query, which will reset the conversation timer again to 2 minutes, so the timer is actually never firing because is continuously moved back 2 minutes.If a notification is received then the WAITFOR(RECEIVE) will dequeue the notification before the 1 minute timeout occurs and, after the application callback is notified, the SqlDependency will again post the same query, resetting the timer again.

After the application callback is notified… Is there a problem with that? Of course, if the callback is lasting longer than 2 minutes (or more precisely the time left from the original 2 minutes when the query was first launched) then the conversation will fire and the SqlDependency infrastructure will be removed. The only question here is if the callbacks are synchronous or asynchronous. A simple breakpoint on my callback and a look at the stack provides the answer:

This stack shows that the application specific callback (the SqlDependency.OnChange) is called synchronously, in the context of processing the WAITFOR(RECEIVE) query results. If this callback exceeds what’s left from the original timer 2 minutes, then the conversation timer will fire and the SqlDependency infrastructure will be removed. One can easily verify this by simply waiting in the debugger on the breakpoint set on the callback. In a short the SQL Profiler will show that the activated procedure was launched and the procedure itself, the service and the queue were dropped. Interestingly enough after the application is resumed the SqlDependency creates a new infrastructure by deploying a new procedure, service and queue.

Of course, 2 minutes to process a callback seems like infinity. But there is one very common scenario that results in such huge times: debugging! When you develop your application you often spend minutes in front of the debugger, inspecting variables and then … discussing with a coworker perhaps, before letting the application resume.

Another thing to consider is that when SqlDependency is used in a normal forms application the callback is usually invoking a form method on the form’s main thread by calling Form.Invoke so that UI elements can be refreshed. The Invoke call will block the callback thread until the UI thread can service the message pump, so if the UI thread is blocked (perhaps in a database call) then the callback thread will also be blocked.

And finally if you simply have a lot of callbacks on the same notification, then the total time to service each callback can add up.

Still 2 minutes is a long time in an application, but if you found yourself faced with investigating mysterious errors showing up in ERRORLOG, one place to look for is this: are you blocking the SqlDependency background thread by any chance?

6 responses to “SqlDependency.OnChange callback timing”

Hi,
thankx for your explanation.
I’m working with Query Notification and the sql server errorlog started to get filled by this error message..my DBA was not happy but fortunately they appear in the development environment.

It happended only once and actually I was not able to replicate it ..
To be precise these were the error messages that were logged:
The activated proc owner.[SqlQueryNotificationStoredProcedure-a48e95dc-7570-4f38-85cc-ceeb3b712a1a] running on queue dbname.owner.SqlQueryNotificationService-a48e95dc-7570-4f38-85cc-ceeb3b712a1a output the following: ‘Cannot drop the queue ‘SqlQueryNotificationService-a48e95dc-7570-4f38-85cc-ceeb3b712a1a’, because it does not exist or you do not have permission.’
The query notification dialog on conversation handle ‘{F09F63A2-3206-DD11-A3C2-0003FF5E09C9}.’ closed due to the following error: ‘-8470Remote service has been dropped.’.

Does the first message has something to do with the esplanation you just gave it has to do with something else?
Thank you

Both error messages you posted are related to SqlDependency. As to say exactly what caused them *this* time, I can’t venture a guess. The many ways that feature can cause errors never cease to amaze me…

I would focus on stress testing. I used to be a tester in a prior life, so here is how I would approach this: create a test suite of your typical application behavior. Make sure each test is independent so that ore tests can be run in parallel. Then run it against a test server in a high concurrent fashion (tens, hundreds of tests ran in parallel). This sort of stress usually exposes the problem. Note that my test would focus on the application, not on the SQL engine, since is likely something in the application triggers this behavior (eg. a premature SqlDependency.Stop or a callback that lingers for too long in the OChange event, just like the original blog post).
Now I reckon that this is a fairly complex endeavor for a very low prize (find the culprit of the Query Notification error message). Other than the annoying message in the ERRORLOG, usually there isn’t any bad effect.