Forum Discussion
iControl timeout
Where can I configure the iControl timeout to exexute a command?
I have two BigIPs driven by iControl. iControl periodically sends synchronisation instruction on the active BigIP. But I have many objects on my boxes and the synchronisation took more than 5 minutes (~ 5.20, 5.50) and the timeout of iControl (seems to be 5 mn) is triggered.
How can I change this 5 minutes timeout?
Thanks,
Als.
- mhite_60883CirrocumulusProbably a knob on whatever method you are using to access iControl. If you are using pycontrol, which uses suds as its SOAP library, you can probably set the suds client timeout.
- mhite is right. The timeout is a property of the client library you are using. What language are you using for iControl? I believe this setting is configurable in .Net and Java but I'm not sure about the other languages.
- Alscion_68122NimbostratusHi,
- I included the code in the iControl java library but unfortunately didn't expose it outside of the iControl.Interfaces class. There is an internal variable m_timeout that defaults to 60 seconds.
private int m_timeout = 60000; // 60000 ms.
The *BindingStub classes I create as members in the iControl.Interfaces class are derived from org.apache.axis.client.Stub which has a setTimeout() method.
In the interfaces class, there is another private method called setupInterface(org.apache.axis.client.Stub stub). In there, I'm setting the timeout.
You could always call the timeout method directly on the object
m_interfaces.LocalLBPool.set_timeout(nnnn);
I haven't tried it but it should work.
-Joe
- L4L7_53191NimbostratusI actually think we may want to look at the problem you're trying to solve. Note that what we're talking about here (in all cases, regardless of the language) are *transport* timeouts. It's likely that you're being caught with such a timeout given the length of those sync jobs. Note that this can happen in at minimum four different spots: the client stack, the client library (via socket options set), the bigip stack on the management port, and the Apache/iControl timeouts set there (which translate to socket options as well). Intermediate devices can do it too, of course.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com