A bug was recently discovered on a legacy HornetQ branch. ActiveMQ 6 doesn't suffer from the same problem, but the test is still valuable. The HornetQ issue is described on https://bugzilla.redhat.com/show_bug.cgi?id=1193085.