.NET Framework Bookmark and Share   
 index > ASMX Web Services and XML Serialization > Web service call hangs and raises deadlock exception
 

Web service call hangs and raises deadlock exception

I am trying to make a web service call to a website and it just hangs with the following exception:

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

Anyone have any ideas?
TheLearner
I doubt that anyone will be able to help you, since you have not posted any details of your application, nor have you posted any code.
John Saunders
WCF is Web Services. They are not two separate things.
Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
Use File->New Project to create Web Service Projects
John Saunders

You can use google to search for other answers

Custom Search

More Threads

• Java(Websphere 6.1 Apaxhe Axis 1.3)/.NET Interoperability: Complex type deserialization problem
• Com Interop problems with OPCDAAuto.dll
• Reflection failure
• How can I create a Proxy Class using WseWsdl3 when I have soap headers on my web methods?
• How do I configure web server to get a web service to run?
• Tracing not working from Webservice
• security for files in web folder
• WSE3.0 client consume Java MTOM enabled web service--cannot download large file
• How to limit the execution time for a web mothod call?
• Repeater + Extended control not working