"clebert.suconic(a)jboss.com" wrote : | | Based on what we talked before, a client connection to a nodeA will always have to faile to a nodeB. A server rule will determine this. | | So it's not totally driven from the client side then? anonymous wrote : | | What we should do then if a connectionState has a non clustered queue on its hierarchy during a connection failure event then? Throw an exception? Disconnect the Consumer? | | I would say disconnect it and any further operations (e.g. receive()) on that consumer should throw an exception. anonymous wrote : | So far I think we could (don't know if we should) reconnect non clustered topics on the new node. We won't be able to guarantee deliveries, but at least we wouldn't interrupt the client. Now if the requirement is to fail over only on ClusteredQueues we should know what to do then. | A non clustered destination is, by definition, non clustered. Therefore there is no expectation of HA for that destination. anonymous wrote : | | I will be able to refactor anything if we get some problem. I'm constructing this piece by piece, we will be able to refactor later. That's cool. I'd just be careful of going too far down the wrong path. Otherwise you may have a *lot* of refactoring to do :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980436#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...