Hello Iñigo-
In short, the cursors are a layer on-top of the persistence store (kahadb or
other) that manages how messages are paged from the store and dispatched to
consumers.
There are multiple message cursors available and they each provide different
capabilities to meet the needs of
, BTree indexes, etc.
In addition to the Message Store, ActiveMQ has another element where messages
are also stored: Message Cursors.
My main question is whether the Message Store and the Message Cursors are
somehow interconnected or if they are independent elements within the broker.
Fo
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
e. if the limit is reached, your producer
blocks or slows down a bit, perhaps giving a consumer time to drain
the destination that the producer is sending messages to. Message
cursors are another way to avoid high memory usage in the broker, by
spooling messages someplace other than memory (u
emory limit or the
store/temp filesize limits, in a way that you wouldn't perhaps need to
address in your producer, i.e. if the limit is reached, your producer
blocks or slows down a bit, perhaps giving a consumer time to drain
the destination that the producer is sending messages to. Message
c
It could be that you're hitting the system memory usage limit. Try
setting a lower memory limit on your queue like 1mb with the
pendingQueuePolicy.
On Fri, Oct 1, 2010 at 6:13 PM, Joe Niski wrote:
> Well, i may have spoken too soon. Tests with a queue's destination policy
> configured like this
Well, i may have spoken too soon. Tests with a queue's destination policy
configured like this:
indicate that the pendingQueuePolicy is ignored if producerFlowControl is
enab
Thanks for the clarification, Dejan.
*Joe Niski
*IS Development | NWEA
PHONE 503.212.3382 | FAX 503.639.7873
NWEA.ORG <3D%22http://www.nwea.org/%22> ** | Partnering to Help All Kids
Learn
On 09/29/2010 01:29 AM, Dejan Bosanac wrote:
> No, producer flow control is on by default with store ba
it possible to use both producer flow control (so producers can
>> fire away while consumers try to keep up with them) AND file-based message
>> cursors (as a second line of defense against ActiveMQ blocking producers, at
>> the risk of filling up the disk)?
>>
>>
; In reading he online docs and "ActiveMQ in Action", i'm left with a question:
> is it possible to use both producer flow control (so producers can fire away
> while consumers try to keep up with them) AND file-based message cursors (as
> a second line of defense against Acti
se both producer flow control (so producers can fire away
> while consumers try to keep up with them) AND file-based message cursors (as
> a second line of defense against ActiveMQ blocking producers, at the risk of
> filling up the disk)?
>
> thanks in advance,
> Joe
> --
>
&g
oducers can fire away
> while consumers try to keep up with them) AND file-based message cursors (as
> a second line of defense against ActiveMQ blocking producers, at the risk of
> filling up the disk)?
>
> thanks in advance,
> Joe
> --
>
> Joe Niski
> IS Development
In reading he online docs and "ActiveMQ in Action", i'm left with a question:
is it possible to use both producer flow control (so producers can fire away
while consumers try to keep up with them) AND file-based message cursors (as a
second line of defense against ActiveMQ blo
ontext:
http://www.nabble.com/Message-Cursors-tf3942330s2354.html#a11182382
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
17 matches
Mail list logo
