Forum Discussion
Mike_Thompson_9
Sep 05, 2007Nimbostratus
Ok, I was finally able to get logging enabled and isolated on the Dev F5 and found some interesting results. First off, I start my test harness application which essentially makes the same call to the ASP.NET web service over and over until it reaches an error.
So, I start the test app, then open the F5 web console and navigate to the ConfigSync menu. Once this is open, I hit the Update buttone once or twice which appears to initiate some SOAP chatter between the two devices. When I do this, my test application stalls and eventually throws a timeout exception:
System.Net.WebException: The operation has timed out
My timeouts are currently set to 45000ms (45 seconds) on both the client and web service, which should be more than sufficient. Also, I am able to duplicate this problem over and over. All that is needed to get this to occur is to click the Update button on the ConfigSync screen while another web service call is being made.
Still trying to get the IOE exception though. However, I do recall seeing some device chatter on or at the same time I received the IOE error in a previous test. Will keep you updated....