Paging files not cleared after consuming messages

[robertjlee]

Looking to avoid the problem where a single blocking consumer blocks the whole topic, we are testing HornetQ-2.2.5.

We have come accross an issue that we believe to be HORNETQ-743.

We have a HornetQ server with a JMS topic, with two subscribers.

When we put a very large number of messages into the topic, it started paging as expected. We then connected a JMS bridge on a second server to each topic subscription, and consumed all messages from each topic in turn. When complete, the number of messages showed as 0, but the number of paging files had not gone down.

We have so far not been able to duplicate this on a small scale, so we're unsure of exactly what the cause was. Could this be the HORNETQ-743 issue? If so, would changing the transaction mode from DUPLICATES_OK to ONCE_AND_ONLY_ONCE be sufficient to prevent this problem?

Also, when we deleted the paging directory and restarted HornetQ, it gave an error on startup, so we don't have any way to recover from this situation without deleting the data directory (which loses the subscription information, which for us means lost messages).

Would we be better off holding out for 2.2.8-final before upgrading?

Thanks for any help.

[clebert.suconic]

I have fixed a few issues in regard to that.

Do you think you could give a try on Branch_2_2_EAP or Branch_2_2_AS? They are the same now.

[robertjlee]

We will try and test again on the new version, but first we need to be sure how reliably that we can see this behaviour on 2.2.5-final.

As it stands it failed once with 500,000 messages (~4k each) on each of two subscriptions over two attempts, and once with 1,000,000 messages (one attempt), but works reliably with 10,000 messages over 5 attempts (and it takes us some time to generate each message as we're pulling them over a JMS bridge in the first place).