Two additional comments: 1) Without full replication (including the list of messages in a destination) NON_PERSISTENT messages will be lost at failover
2) There needs to be a mechanism to cope with both the client and server failing at the same time. e.g. Before/After server failure Queue: empty Client1: message1 But during the failover Client1 fails. This would need some sort of timeout to detect that Client1 didn't transparently reconnect. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850127#3850127 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3850127 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
