views:

14

answers:

0

I have a system consisting of two parts: WCF server (console) and client (WinForms). Server publishes a service for remote access to the database, and client connects. Everything runs smoothly, client is able to read database documents, attachments and so forth. However, after 60 seconds running in debugger, the following client problem is being reported by VS:

The CLR has been unable to transition from COM context 0x357660 to COM context 0x3577d0 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.

It seems something is wrong in that regard, but I can't figure out what exactly can be causing that issue..

Would appreciate any assistance.