Hi Iranga, What are the failover options you have used in the connection string? Are there 'retries' and 'connectdelay' options configured. They determine the number of times a connection to a broker will be retried and the the length of time to wait between successive connection attempts before moving on to the next broker in. Have we tried with setting retires to 1 and connectdelay to 0 ( which are default values) so then the broker will try to connect immediately to the next one available?
Thanks! On Thu, Mar 13, 2014 at 3:59 PM, Iranga Muthuthanthri <[email protected]>wrote: > Hi All, > > In a MB message produce consume scenario for fail over, if the message > producing MB node fails before delivering all the messages it was observed > that there was a message loss(by observing the Cassandra queue count). > > What are the workaround possible for this considering the guaranteed > message delivery model. > > Note: The message consuming and producing MB nodes are the same. > > > -- > Thanks & Regards > > Iranga Muthuthanthri > Technical Lead - QA > (M) -0777-255773 > -- Ishara Premasada Software Engineer, WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ <http://isharapremadasa.blogspot.com/>Twitter : https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile : +94 714445832*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
