Forum Discussion
Dec 31, 2009
A couple of questions:
1. Is this a client .Net app or a web based ASP .Net app?
2. Are you using the iControl .Net assembly?
I can't think of a reason why this would occur for a windows based app since the iControl calls are completely independent. Each request establishes a new connection with it's own set of credentials. There is no built-in keep-alive connections in the default .Net bindings. I've run load tests for days with my client apps and haven't run into any connection issues.
The one thing I've seen with web based ASP .Net apps is that there is a known issue in the WebClient code that can cause connection errors if too many parallel requests are made. It doesn't sound like that is your issue but if it is let me know and I'll dig up the Microsoft KB article.
Can you code your code to catch the exception and retry the request? If so, does that work or are all subsequent requests failing. A "cannot connect" error implies that there is something going on before it gets to the BIG-IP but it's hard to tell without a trace of some sort.
-Joe