HornetQ have had a few bug fixes after 2.3.0. you should try its latest releases.
I believe this issue would be fixed on later releases but if it's not the case you should provide a test replicating this issue and raise a forum post or if you are absolutely sure you have replicated the issue on a test with the latest release you should open a bug fix request at JBoss JIRA on the project HornetQ.