2

I have a WCF Service which Communicates to multiple WPF Client Applications. The Service uses NetTcpBinding in duplex Mode. Now I have 2 Functions which are called from the Server to notify each Client. One function is called every 50ms with a little amount of Data. (This function is invoked for every Client in a different Task!). The other function is called once, when the client registers on the Backend. This function submits a large dataset to the client.

The problem now is: when the function with the large Dataset is invoked (for one new client), on all clients you see, that they don't get data from the function with the LittleDataset. When the large call is finished everything works as expected.

Is there any way I could solve this? What more infos do you need?

ServiceMode=Session, Concurrencymode=Multiple, UseSychronisationContext=False

BenMorel
  • 34,448
  • 50
  • 182
  • 322
Jochen Kühner
  • 1,385
  • 2
  • 18
  • 43
  • This doesn't surprise me - the way WCF supports duplex has always been a bit flaky. Hardly anyone uses tihs feature. If possible you would be much better off using one way operations over netmsmqbinding than invoking callbacks accross a duplex binding. – tom redfern Sep 24 '13 at 09:58
  • Is there any Document where you can see that this is Problematic? I can't use MSMQ because I also use Silverlight Clients. – Jochen Kühner Sep 24 '13 at 17:25
  • 1
    I solved, by changing the order of my callbacks, and Blocking my small calbacks while th big one is active. But it makes no sense to me that it is now working, and before not... – Jochen Kühner Sep 24 '13 at 17:26
  • @JochenKühner how did you achieve this, I am facing similar problem – DoctorAV Feb 03 '16 at 06:50

0 Answers0