Hi,
Yes, when you configure the client with the MB nodes in the connection
string if the publishing / subscribing MB node is down at that time the
client will fail-over to the next available node.
Regards,
Jason
Jason De Silva
*Software Engineer - QA*
Mobile: +94 (0) 772 097 678
Email: jas...@ws
Thanks for the answers.
So, the failover is performed by the client, is that correct?
Thanks,
2018-03-06 22:22 GMT-03:00 Jason De Silva :
> Hi,
>
> Yes, you need to provide the list of MB nodes in the connection string in
> jndi.properties. Please refer [1] for an example on how you can set it
Hi,
Yes, you need to provide the list of MB nodes in the connection string in
jndi.properties. Please refer [1] for an example on how you can set it in a
round robin manner.
[1]
https://docs.wso2.com/display/MB310/Connection+URL+Format#ConnectionURLFormat-Example
Regards,
Jason
Jason De Silva
*
Hi,
The steps to configure clustered Message Broker is in [1] and the steps to
configure the broker nodes are in [2].
[1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+Message+Broker
[2] - https://docs.wso2.com/display/CLUSTER44x/Configuring+the+Broker+Nodes
Thanks,
Regards,
On Wed, Mar
Hi,
When we have a cluster of WSO2 MB how is the correct way to configure the
jndi.properties to connect to them?
Should we have a list of the cluster members in the connection string?
Does someone have an example of a similar scenario?
Thanks,
--
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certifi
