Failure while reading events on remote event-base replication might cause a connection leak

When using remote event replication, during the connection initialization, Artifactory tries to read events from the connection that it just opened. In case of failure (i.e. IOException while event parsing failure) Artifactory will try to open a new connection, but leak and not close the previous one. As the remote event replication uses the same http connection pool of the actual remote repository, this can quickly causing the repository to be non responsive, and eventually, causing Artifactory to be non responsive as requests to this remote repo will pile up and fill the entire Tomcat requests queue/pool so other requests cannot be served.