#891 Missing fail-over code in HttpConnection
Closed: Fixed None Opened 10 years ago by edewata.

The base/server/cmscore/src/com/netscape/cmscore/connector/HttpConnection.java has multiple constructors but they don't seem to be implemented consistently/correctly.

public HttpConnection(IRemoteAuthority dest, ISocketFactory factory, String op) {

        String host = dest.getHost();
        // we could have a list of host names in the host parameters
        // the format is, for example,
        // "directory.knowledge.com:1050 people.catalog.com 199.254.1.2"
        if (host != null && host.indexOf(' ') != -1) {
            // try to do client-side failover
            boolean connected = false;
            do {
                connected = Connect(host, mHttpClient);
            } while (!connected);
        } else {
            mHttpClient.connect(host, dest.getPort());
        }

}
public HttpConnection(IRemoteAuthority dest, ISocketFactory factory, int timeout, String op) {

        mHttpClient.connect(dest.getHost(), dest.getPort(), timeout);

}

I just want to put a reminder here for when we get here:

Before making any changes, find out if it was done by design: where if a "timeout" is specified, then no "fail-over", and vice versa.
And if it was really the case, to consider if there should not be such limitation and we can have the design changed (and documented per change)

Proposed Milestone: 10.2.2 (per CS Meeting of 09/17/2014)

Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog

Fixed in master: cc8f6468bb9f509d16ed526e42d546aaa2ae9ed3

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.2.6

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1458

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata