My current understanding is, that only the mdb's on the coordinator node will be able to find the destination; the remote mdb's simply wont find the destination, since they use local jndi for lookup. To force them to use HA jndi, you could use this name @ActivationConfigProperty(propertyName = "destination", propertyValue = "jnp://localhost:1100/topic/sometopic"), but i dont like the fact that this port 1100 is in my configuration files (or annotations), because this means my ear file will only work on a jboss without port-shifts (org.jboss.services.binding.ServiceBindingManager). Is it possible to use some {jndi.ha.port} expression inside this jndi-name? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176514#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...