No, that is not the expected behavior :-) It has been a while, but I think that we have a test for this. Can you try providing a test case for this? The primary should start responding to heartbeats and send its own re-route command.
On Tue, Mar 23, 2010 at 6:29 PM, philip <[email protected]> wrote: > I have been experimenting with the RBS LoadBalancer functionality and > it broadly works as I would want, when the primary balancer goes down > the secondary balancer notices the heartbeat messages have stopped and > picks up the baton by sending ReRoute messages to interested parties > to receive new messages. The only problem I have found is that when > the PrimaryLoadBalancer restarts the secondaryloadbalancer won't give > up! in fact the only way to reactivate the primary is to restart the > sending and receiving buses which seems a little brutal. Is this the > expected behaviour or have set it up incorrectly? > > > > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rhino-tools-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
