When a resource provider driver is disconnected, it fails to reconnect.

If the resource provider manager closes the HTTP connection of a resource provider, the resource provider should reconnect itself. For that, the resource provider driver will change its state to "DISCONNECTED", call a disconnected callback and use its endpoint detector to reconnect.
This doesn't work in a testing environment where a ConstantEndpointDetector is used. While the resource provider is notified of the closed HTTP connection (and logs End-Of-File received), it never disconnects itself and calls the disconnected callback. Discarding HttpConnectionProcess::detection in HttpConnectionProcess::disconnected doesn't trigger the onAny callback of that future. This might not be a problem in HttpConnectionProcess but could be related to the test case using a ConstantEndpointDetector.