I have a Silverlight 3 application which needs to call WCF service. The WCF service in turn calls an ASMX web service. When the WCF service call completes, the silverlight UI needs to be updated.
WCF is being called in async.
The thing is that the Silverlight app needs to call the WCF method(which later calls asmx internally) hundreds of time. I understand that because it is in aSync, hundreds of threads will be spawned, so I have coded in a check to ensure not more than X time does the WCF function gets called. Only when 1 call complets, do I add one more call. I hope this will keep a check on the total number of threads. What is the ideal value of that X value? I am ona simple XP machine with dual core CPU and 4 GB ram.
As the WCF calls get completed, I need to show progress bar on the silverlight UI.
This works fine for smaller number of calls, but when i need to make say around 10000 calls, after some time I get a timeout in the Silverlight’s WCFCompleted method. I feel I may be going in a deadlock?
My WCF is configured to be multiple concurrent.
Every time one WCF call completes, it updates the UI… can that be causing this deadlock?
Any ideas anyone? I am stuck bad and lost here.
I later seemingly solved the issue by :
1) converted asmx service to WCF
2) Increased WCF timeouts from 1 minute to 5 minute
3) Instead of updating UI progress bar on every Completed callback, I am now using a timer which updated UI say every 30 seconds only.