For MDB's deployed in the all folder you don't need to do anything: they find the
destination and subscribe, whether it is remote or local; and when the coordinator-node
dies, they resubscribe as soon as the new coordinator-node is ready hosting the
destinations. So this makes me believe that the @Resource ConnectionFactory injection is
cluster-aware somehow.
For client side lookups you should use the right jndi parameters and port 1100 instead of
1099: this will make sure the client-side proxy finds a working node.
For @EJB i dont think this would make sense since it meant for injecting local
dependencies.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180163#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...