I've replaced the following hornetq jar files in my jboss 6.1 AS:
with the 2.2.14.Final version
and restarted jboss.
Everything still seems to work with this new version, however the problem did not go away.
Is this a bug in hornetq?
Can we, in any way, force the failedQueue to do some kind of "refresh" or reload?? Perhaps by consuming a message en rollback immidiately after receiving the message?
Consuming large volumes of messages on the queues seems to go OK when using paging.
I really appreciate your help, since this problem is occurring in our production environment!
Jan van de Klok