1

I have a windows phone application that uses WCF services to get and store data on the DB. I added a service reference to the WCF service and VS generated the client proxy and the configuration file.

The problem starts when I try to call methods on the server.

The first call causes a timeout, the server doesn't even receive the request. Only in the second call the server receives the request.

Win7MobileServiceClient client = new Win7MobileServiceClient();

client.GetUserCompleted += new EventHandler<ServiceReference1.GetUserCompletedEventArgs>(client_GetUserCompleted);

client.GetUserAsync(int.Parse(txtID.Text));

Thanks

kadir
  • 1,417
  • 11
  • 35
user556882
  • 121
  • 1
  • 5

1 Answers1

0

This is probably due to the warm up process of service. First time that a WCF service is invoked it takes some time (I think is compiling it). It will happen again if you recycle app pools.

In order to be sure try this

  1. Deploy WCF Service
  2. Invoke WCF service from windows
  3. Invoke it from windows mobile

If this is the case probably the reason is that default timeout in windows mobile client maybe is smaller than stantaderd (1min). There is a number of solutions you can do like

  • Increase windows mobile time out
  • Invoke service everytime you deploy it (for example have some sort of smoke test in Selenium. The problem of this approach that you will have again same problem after recycling of app pools)

You can check this similar question: WCF Performance Slow for the first call

Community
  • 1
  • 1
Oscar Foley
  • 6,817
  • 8
  • 57
  • 90
  • I don't think that is the problem. If I try to invoke the method twice in a row, the method works as expected. – user556882 Apr 04 '12 at 13:08
  • Then... you have a problem :) Try comparing app.config of client and service and check that buffer sizes and message sizes.. – Oscar Foley Apr 04 '12 at 13:58
  • Maybe invoking emthod twice in a row give times to server to build. Say that timeout is 10 secs and takes 11 to build.. first invocation fails but second works because it is 1sec to build + 1 sec to execute... – Oscar Foley Apr 04 '12 at 14:13
  • I tried all...Still the same proplem. I found that the problem is in the windows phone client. I call the service async from console, win forms and silverlight applications. Maybe you wrote something similar? with wcf and windows phone client – user556882 Apr 04 '12 at 20:35