On Tue, Jan 20, 2009 at 9:21 PM, Carl Trieloff <[email protected]>wrote:
> Rajith Attapattu wrote: > >> During testing I noticed the following. I would appreciate if folks who >> are >> interested in this area comment about these observations. >> >> a) If a single broker is defined in the URL, by default >> FailoverSingleServer >> is chosen. >> In this case, I believe we should default to no failover unless explicitly >> specified. >> > > no, that is not correct. This list of URL's provided in this list are the > brokers to try connect to the cluster with. Once > the client has connected to a broker cluster the cluster notifies the > client with the updated list of URL's in the cluster > as nodes get added or removed from the cluster. > Here I was refering to the case of a non clustered broker. That is when there is only a single broker defined in the connection URL. Even in the case of a clustered broker, currently the java client only iterates through the list provided in it's connection URL. It does not subscribe to the failover exchange to get an updated list of brokers. This feature will be added in the near future. > So on initial connection the client should iterate the list. once connected > it should get an updated (full) list from the > broker which replaces this list every time the broker sends the client a > new list of URL's > > Carl. > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/
