This node works similarly to the Start WebDriver node, except that it relies on a global pool of WebDrivers respective browsers. When the node is executed, it will try to retrieve an existing, idle WebDriver with the specified configuration from the pool, and only start a new one in case no WebDriver is available.
Instead of quitting the WebDriver (e.g. by resetting this node, or by running a Quit WebDriver node), it is handed back to the pool and can be reused later. WebDrivers managed by the pool will be quit simultaneously with KNIME.
The node performs a simple health check before handing out a pooled WebDriver. In case a WebDriver is not responding (e.g. because it has crashed, or it was killed by the user) it is eliminated from the pool.
Note, that the pooling mechanism is primarily intended for speeding up workflows which would start new browsers very frequently (e.g. in a busy loop). Pooled drivers keep their settings (cache, cookies, data, history, etc.), it is therefore not advisable to use the pooling mechanism when you require a “clean” browser, e.g. during testing.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.Try NodePit Runner!
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to firstname.lastname@example.org, follow @NodePit on Twitter, or chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.