Well, we could add such a switch, but it doesn't tackle the problem of all messages going to one node every time you do a normal startup.
Also, going ahead, most people want to move away from the old style "JBoss MQ" model where you have a single shared database which all nodes use - since this turns into a performance bottleneck. For better scalability, we're going to support each node having its own file based persistent storage, or it's own database. (Of course we'll support the old model too) Typically all the file based stores would be persisted on some kind of SAN or shared file system with redundancy built in. If a node fails, another one takes over. When starting up from complete power failure, if a particular node doesn't start - e.g. the box is dead, then you could just start it on another node with the same server id, this could be done with a simple script. You could probably do something similar then you wouldn't have to worry about starting the node from the same crashed box. But having all messages on one node is not really a scalable solution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063479#4063479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063479 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
