One of our community contributors is currently updating the documentation on how to get clustering with JMS. Kurt is also working on fail-over support (essentially clustering for high availability). Once these are done, we'll report them via the forum and you can check them out.

There is no official GA release of 4.2 yet, just two milestone releases. Clustering over JMS is simply some configuration changes, whereas the fail-over is new code. However, there have been some significant changes between 4.2MR2 and the current trunk, so we would recommend you use the trunk if possible (via anonsvn). We're probably going to put out another milestone release next month.

Hi pablodiablo

You can surely bring up more then one service instance listenening to the same bus (jms queue). This would give you some basic loadbalancing and failover. See also:

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107227

Right now we are working on enabling loadbalancing/failover of service instances listenening to *different* buses. So you can play thicks with load balancing over different ftp servers, or different jms queus or even different jms providers. The latter should be on the trunk in the next week or so, examples and docs will follow after that. I'd be great if you'd want to work with us to build a proof-of-concept, wich can work as a Quickstart later, along with documentation.

Cheers,

--Kurt

"kurt.stam@jboss.com" wrote:
Right now we are working on enabling loadbalancing/failover of service instances listenening to *different* buses. So you can play thicks with load balancing over different ftp servers, or different jms queus or even different jms providers. The latter should be on the trunk in the next week or so, examples and docs will follow after that.