Correct except for 6) which is false. There has been no such change in 4.0 so what is the basis for your view on this point?
Ok, Serverless JMS is a JBoss 5 feature, not 4.0.x.
What exactly does it mean to be a JMSProvider?
I got the impression that the JMSProvider node has got the one and only instance of each topic and queue that is used by the entire cluster. My tests seem to prove that I have either misunderstood this, or that something is wrong with my setup.
I have two nodes in a cluster, set up according to the HAJMS Wiki. Debug printouts from my clustered publisher session beans and my message driven receiver beans seem to indicate that there is one instance of the topic on each node.
If I turn off the message driven receiver bean on one node, and let the publisher continue on that node, the message driven beans on the other node does not start to consume the messages published by the publisher on the first node.
Version: JBoss 3.2.6RC1
Platform: Windows XP SP2
Cluster: Two server instances on the same machine, according to this wiki: