"ataylor" wrote : anonymous wrote : But this does not explain how an failover works with an MDB | | MDB's are outside the scope of JBM. You can find more information from the app server guys or the app server docs. |
;-) The app server 4.2.2 docs don't describe how jms works with new messaging. Even there's a note, that future revision will use new jboss messaging. Also it notes that messaging will work completely different from jbossmq. The newer 5.0.0 jbossas doc is not accessible for me. ( (http://labs.jboss.com/file-access/default/members/jbossas/freezone/docs/Clustering_Guide/beta500/html-single/index.html) anonymous wrote : | anonymous wrote : | | You should have if a node crashes, the other must do the work. Messages should not be left unprocessed in a (local) queue anonymous wrote : | | | | Messages will never be left unprocessed, The MDB on node A will consume messages from the queue on node A, and the MDB on node B from the queue on node B. If node A goes down, its state is replicated on node B so the messages will then be consumed on node B. :o) My example even does not work. But as I understand, you are (as messaging-developer) out of scope for this problem. Which forum I should post to? Is there another way to get the latest jbossas (beta) docs? And last but not least what is your opinion of using jboss messaging together with jbossas 4.2.2 in a clustered environment? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162778#4162778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162778 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
