MDB load balancing

[justkeys]

http://docs.jboss.org/jbossas/jboss4guide/r4/html/cluster.chapt.html

and 16.6.1.3 suggest that mdb's on all node's might be consuming from a single queue (on the master node). Is that by default so; and what is this unclear explanation in 16.6.1.3 about?

[justkeys]

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?

[justkeys]

After some more seach i found out that the all-deployment does use ha-jndi to look up queues and topics. So each node will be able to start the mdb's, whether the queue is remote (node is not coordinator) or local (node is coordinator).

So this single question remains: what's the relevance of http://docs.jboss.org/jbossas/jboss4guide/r4/html/cluster.chapt.html#clustering-jms-loadbalanced ?