Forum Discussion
Mar 01, 2010
Ok, I get you know. iControl is implemented with FastCGI in a single connection configuration that essentially implements a first-in-first-out (FIFO) queue. The process will accept a request and then process one after another in sequential order.
In this thread, I discuss how to enable iControl tracing
http://devcentral.f5.com/Default.aspx?tabid=53&forumid=1&postid=16431&view=topic
Click here
It will dump the inbound parameters to the /var/log/ltm file including the first 2k of the inbound SOAP request. This log occurs after the request has made it out of the queue and when it hits the web server for processing.
When I first developed the fastcgi implementation, I tested this with 100's of parallel connections of getting/setting values and didn't see any issues with some calls not returning error codes but not doing what you requested. Now, that was a few versions of BIG-IP ago, but from what I'm aware, the implementation hasn't changed.
I'll see if I can simulate a test that does this with 1000's of objects and parallel requests to see if I can reproduce the issue. In the mean time, this most likely will be a issue that you'll have to bring up to product support because it sounds like you are doing everything right. The only thing I can think would be if your parameters are not defined correctly, but if it's working in single mode, just not parallel, then that wouldn't likely be the problem.
-Joe