Open gabrielprioli opened 8 years ago
I've attempted to solve it by adding Options.refresh()
(which always sets a new connection manager - View file, line 72)
However, I don't really know if this is the correct fix as the plugin sometimes failed and removing it would make it work again. Perhaps some conflict with frequently creating new connection manager objects.
The issue
After a change in plugin properties (plugin name, username, password, test name, test type, etc.), the
teardown()
will be executed and thePoolingHttpClientConnectionManager
(from the underlying libraryhttp-client
) will be closed. The next execution of the plugin fails because the connection manager is shut down.Please see captured log below with commentaries:
Last successful execution (before property change) (16:04):
First execution (after property change) (16:09). The execution starts with calling
teardown()
, as seen by the "Shutting down Unirest" log message.Now, the
execute()
begins, trying to authenticate. However, a Unirest exception is captured and theConnection pool shut down
exception is thrown.How to reproduce