SqlDependency.Stop() called from SqlDependency.OnChange handler freezes - by Oyster

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


4
0
Sign in
to vote
ID 314039 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/1/2007 8:45:59 AM
Access Restriction Public

Description

If I am calling SqlDependency.Stop() from inside SqlDependency.OnChange handler for the same DB then SqlDependency.Stop() call freezes forever and application starts consuming all the CPU time available.
Sign in to post a comment.
Posted by Oyster on 2/2/2009 at 8:52 AM
Why won't you fix this issue? Give some description please because issue is really quite disturbing - I was hoping that it's fixed in .NET FW 3.5 but it obviously not.
Posted by Microsoft on 12/1/2007 at 10:11 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 12/1/2007 at 10:04 PM
Thank you for your feedback. We are currently investigating. The investigation process normally takes 7-14 days. If this issue is urgent, please contact support directly (see http://support.microsoft.com).

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Posted by Oyster on 12/1/2007 at 9:33 AM
I have verified this issue on .NET Framework 2.0 SP1 - it's still reproducible on Service Pack 1.

I also want to notice that problem described by my colleague Dmytro Kryvko here - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=639623&SiteID=1 - probably has the same reason - infinite cycle inside query notifications-related System.Data code which never stops execution (please see Readme.txt from attached archive for more details).