you are using a durable subscriber but with non persistent messages.
Because a non persistent message is not in the brokers messages store,
it needs to be locally persisted by the durable subscription cursor,
so it uses the filebased message cursor and replays the messages to
that.
I think what you
I haven't explicitly configured any cursors on the Topic. From the
documentation it seems like the default is the store based cursor, but when
looking at the ActiveMQ Transport thread stack trace I noticed it was also
using the "FilePendingMessageCursor". Can I explicitly configure the broker to
That is expected for the file based cursor. It tries to proxy the
store, so the entire store is replayed through the cursor to ensure
correct message order. This behavoour only makes sense if the
underlying store is very slow, which in your case, kahaDB, is not.
The store based cursor will be a be
Hi,
So I added a custom subscription recovery policy to ActiveMQ-5.3.2 that stores
messages in a different instance of Kaha Db. To load test this recovery policy
we sent close to ~ 82 million messages(24 hours worth of messages) to the topic
that has the recovery policy enabled on it.
When conn
