Tuesday, November 30, 2010

ContextSwitchDeadlock Exception

This ran into this strange exception which I haven't seen before.

The CLR has been unable to transition from COM context 0x33c5458 to COM context 0x33c55c8 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.
More on this exception and how to disable it from being thrown can be found here http://msdn.microsoft.com/en-us/library/ms172233(v=VS.90).aspx  and here http://blogs.microsoft.co.il/blogs/adlaim/archive/2007/08/06/The-CLR-has-been-unable-to-transition-from-COM-context.aspx

In my case, I believe the conditions that led to this exception to be thrown were caused by a call to a web service that was taking too (long > 60) seconds to either return or timeout.

No comments:

Post a Comment