Looked through it briefly: For the Apache based client, the ConnectionManager has a `closeIdleConnections()` method, which's timeout you can set to 0, so it should force-close all connections.
For the Akka based client, you need to get access to the `Http.HostConnectionPool`. You'll then have access to its underlying gateway which has a `shutdown` and a corresponding `startPool` method, which is documented to play just nice in tandem with `shutdown`. Alternatively, we can opt to just regenerate the hostConnectionPool itself for this case, if we think that's the safer alternative. Measuring will tell if this is necessary optimisation though. [ Full content available at: https://github.com/apache/incubator-openwhisk/pull/3976 ] This message was relayed via gitbox.apache.org for [email protected]
