n your case, kahaDB, is not.
The store based cursor will be a better match a it does not attempt to
proxy the whole store, rather it reads it in batches and only starts
to cursor new messages in memory when the store is exhausted.
On 8 March 2011 02:06, Anirudha Khanna wrote:
> Hi,
>
> So I a
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
Hi,
We are attempting to write a custom subscription recovery policy for ActiveMQ
5.3.2, which allows subscription recovery of messages received on a topic over
the past N days. Since the number of these messages could be very large, we are
thinking of storing these messages in either an RDBMS
al destinations such that topic subscribers each get a queue.
On 23 February 2011 01:37, Anirudha Khanna wrote:
> Hi,
>
> We are evaluating ActiveMQ as a solution for our messaging broker. One of the
> requirements is to be able to replay messages received on a destination for
>
s are apparently stored in
memory. I am curious what is the solution other users have implemented, if at
all, to solve the replay problem.
Thanks,
Anirudha Khanna
Hi,
When sending messages using persistent mode and useAsyncSend=true, I noticed
that the producer throughput is roughly 10x more as compared to when
useAsyncSend=false. What I am trying to understand is whether it is safe to use
this option if we want to guarantee that all the messages that a
Hi,
I am a developer working for Yahoo! Inc. and we are currently evaluating
ActiveMQ for using it as streaming solution for Yahoo serving applications. We
have a requirement for the streaming platform to be able to persist messages on
a topic, till the set message expiry is up, even though the
