Webservice timing out

Question

I added a web reference to my VS 2005 console application
as http://servername:8004/BEWCFService?wsdl

Then in my code I added:

BEWCFService beWCFSvc = new LTL.CMIEngineFramework.BEWCFSvc.BEWCFService();
BEWCFSvc.BorrowerContactInfo[] borrowerContactInfo = beWCFSvc.GetBorrowerContactNumbers(LeadID);

The call to this WS times out with :"The CLR has been unable to transition from COM context 0x1a3008 to COM context 0x1a3178 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."

I used WCFStorm to call this WS and the result comes back in an instance, so I don't think the WS is a problem.

I deleted the web reference a few times and added it back again. did the clean and rebuild operations.

Please advise.

Thanks

Answer 1

Hi n2201,

 

 

Welcome to MSDN forums!

 

Based on my research, this time out could probably be caused by ContextSwitchDeadlock Managed Debugging Assistant (MDA).

 

Here is an similar thread related to this issue,

http://www.tech-archive.net/Archive/DotNet/microsoft.public.dotnet.general/2006-08/msg00218.html

 

The reasons is stated in this MSDN blog,

http://blogs.msdn.com/jmstall/archive/2005/11/11/ContextSwitchDeadLock.aspx

 

You can turn off the MDA globally following this steps,

 

1) Open your project in Visual Studio 2005

2) Click on the Debug menu on the main menu of the Visual Studio IDE.

3) Choose the Exceptions option (Debug -Exceptions).

4) The Exceptions window will open.

5) Expand the "Managed Debugging Assistants" node.

6) Uncheck the ContextSwitchDeadlock option under the Thrown column.

7) Click on Ok and close the Exceptions window. You can now run your

applicationand test it to see whether the exception occurs again.

 

For more details, you refer to this thread,

http://bytes.com/topic/visual-basic-net/answers/647186-mydataadapter-fill

 

 

Does this work for you? If you have any questions or concerns, please update the thread and we will have a further discussion.

 

 

Best Regards

Yichun Feng

MSDN Subscriber Support in Forum 

If you have any feedback on our support, please contact [e-mail]

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Answer 2

Hi n2201,

 

I am writing to check the status of the issue on your side.  Would you mind letting us know the result of the suggestions? 

If you need further assistance, please feel free to let me know.   I will be more than happy to be of assistance.

 

Have a nice day!

 

Best Regards

Yichun Feng

MSDN Subscriber Support in Forum 

If you have any feedback on our support, please contact [e-mail]

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.