Was this ever resolved. What was the solution you employed and did it work?
I ended up using
That seems to fall in line with what I had to do to get it working.
Too bad, required a code change to upgrade HornetQ.
From HornetQ 2.2+ we have been more diligent with version and api compatibilities.