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: [email protected] WSO2 Inc. www.wso2.com <http://wso2.com/signature> On Mon, Mar 12, 2018 at 7:20 AM, Júnior <[email protected]> wrote: > 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 <[email protected]>: > >> 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#Co >> nnectionURLFormat-Example >> >> Regards, >> Jason >> >> Jason De Silva >> *Software Engineer - QA* >> Mobile: +94 (0) 772 097 678 >> Email: [email protected] >> WSO2 Inc. www.wso2.com >> <http://wso2.com/signature> >> >> On Wed, Mar 7, 2018 at 12:47 AM, Júnior <[email protected]> wrote: >> >>> 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 Certified SOA Associate* >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> > > > -- > Francisco Ribeiro > *SCEA|SCJP|SCWCD|IBM Certified SOA Associate* >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
