Hi - we have a four node HornetQ cluster in place which is handling many different consumer/subscribers.  The services that connect to the queues and topics are very busy processes.  They pretty much run all day long non-stop dumping and picking up messages.  What I see is that a process might have up to 6 consumers and all the consumers can potentially wind up on the same 1 or 2 nodes.  Generally the only way I've seen to sort of better spread these is to restart the services and have them create new connections.

Is there anything that I may be able to configure on the HornetQ side to sort of detect this and better spread the consumers/subscribers?

Thanks,

Ken