We have discovered several advantages to a NOT so tight integration with JBoss. Our projects and our customers wish to be able to run multiple Hornetq instances configured as clusters with HA backups spread out and maintained over the same physical hardware but not inside or affecting or affected by the JBoss clusters that we build. The clustering and backup synch-restart requirements simply do not leave the applications we deploy in JBoss well-enough-alone in a complex installation.
Basically we want to be able to separate the two. We've had HornetQ inside JBoss and we are pretty sure we want it outside.
((Noting (as we have noted to the customer) that for best practice we really REALLY want separate disks for the data stores in order to get the performance everyone expects))
To do this with all the applications we have built inside JBoss clusters using HAJNDI to get their connections to Hornetq, the most appropriate and (it appears on the face of it, simplest) thing is to integrate HAJNDI with the standalone HornetQ. I perceive a potential downside if the Hornetq arrangement is configured so that apps on a machine in the cluster wind up often using HornetQ served from some OTHER machine elsewhere in the cluster. The potential for non-trivial slowdowns in network transport has to be considered.
So I will be trying to do this with 2.1.0 Final (or GA if that turns up soon) and JBoss 4.2.3.GA, and/or 5.1.GA ... The immediate benefit is obvious if we are thinking of upgrades and changes.
My plan at present is to use the 2.1.0.Final as a base, and pull the HAJNDI libraries and config from the specific version of JBoss that I am using rather than to try to force the JBoss into a changed HAJNDI and modify the JNDI to the HAJNDI config.
With a little help from the real masters here, I will I think, refine this into a little step-by-step process.
Anyone with suggestions (or who has already done this !) please feel free to discuss. I am only starting now, and I have a daytime project to distract and divert me :-)
Note: There is already a discussion of integrating the standalone Hornetq with JBoss HERE
Hmmmm.... maybe need to make that part of the step-by-step too. It was relatively simple but its not useful to have to pick the details out of that discussion. Bill did us a big favour by all his hard work on that.