In the context of Qpid JMS and Dispatch you have a couple of main options.

First, update the connection factory JNDI properties / URI details you
are using for the connection factory, as mentioned.

Also, the router can be configured advertise failover server details
to clients (and other routers) as they initially connect. For example,
with a current 1.2.0 router, adding "failoverUrls:
host:5673,host:5674" to a listener (e.g, for host:5672) config entry
would cause it to advertise those servers details. A Qpid JMS client
configured for failover which then connected to host:5672 using its
already known details would notice these and change to using
host:5672,host:5673,host:5674 as its current server list (this
behaviour can be tweaked via the failover.amqpOpenServerListAction
option, 
http://qpid.apache.org/releases/qpid-jms-0.35.0/docs/index.html#failover-configuration-options).
These updates are transient, so if the app was restarted the client
obviously wont know about any new servers until it had connected to
one of its previously known servers which can tell it about it them.

Robbie

On 20 July 2018 at 17:15, VERMEULEN Olivier <olivier.vermeu...@murex.com> wrote:
> Hello,
>
> I have a messaging cluster with multiple dispatch-routers and multiple 
> brokers (Broker-J).
> I'm using Qpid JMS for the client and when creating the connection factory I 
> pass the URIs of all the dispatch-routers to support failover.
> The question is, what happens if I want to scale up my infrastructure and 
> start a new dispatch-router?
> Is there a way for the existing connection factories to take the new 
> dispatch-router into account or should I recreate them?
>
> Thanks,
> Olivier
> *******************************
>
> This e-mail contains information for the intended recipient only. It may 
> contain proprietary material or confidential information. If you are not the 
> intended recipient you are not authorised to distribute, copy or use this 
> e-mail or any attachment to it. Murex cannot guarantee that it is virus free 
> and accepts no responsibility for any loss or damage arising from its use. If 
> you have received this e-mail in error please notify immediately the sender 
> and delete the original email received, any attachments and all copies from 
> your system.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Reply via email to