We would have to keep the flow control status per publisher across the cluster I suppose. Is there a way through client to retry publishing after sometime ? Which can be set through the AMQP url ?
Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +94777688882 On Fri, Mar 20, 2015 at 3:32 PM, Pumudu Ruhunage <[email protected]> wrote: > Hi All, > > We did fail over testing on mb nodes in AWS instances and came across > following issue. Following is the scenario tested in cluster. > > 1. Start 2 node mb cluster with nodeA (coordinator), nodeB. > 2. Add queue subscriber "MyQueue" to nodeB. > 3. Start publish "MyQueue" queue messages to nodeA. > 4. After flow control enabled in nodeA, disconnect nodeA from the cluster. > > At a moment where flow control is enabled for the publisher, the > coordinator is killed. Even though(assuming) that the publisher moves to > the other node, it is still under flow control and the node does not > disable the flow control for the publisher. Therefore the publisher does > not publish any messages afterwards. How can we overcome this issue ? > > Regards, > -- > Pumudu Ruhunage > Associate Software Engineer | WSO2 Inc > M: +94 779 664493 | http://wso2.com >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
