I will look at IndirectMessageReference more closely. The pendingMessages
map does have an IndirectMessageReference for each dispatched message. And
each IndirectMessageReference contains an ActiveMQTextMessage (in my case)
which is the fully realized message.
So the trick is to know when the
When I use the default store cursor, then the system will end up blocking.
This is because the cursor reaches the 70% watermark and stops dispatching
messages to the consumer. This is also not viable for us because then there
is no way to get all the messages to the consumer it need to complete t
>From a fix perspective, have a look at
org.apache.activemq.broker.region.IndirectMessageReference
it seems to be what is needed but I don't think it is currently
utilised to the full or fleshed out.
On 24 February 2012 11:52, Gary Tully wrote:
> That seems to be a reasonable expectation, that t
That seems to be a reasonable expectation, that transaction size is
not limited to available memory.
There was some work on trunk to have an in-memory send transaction
overflow to a temp file but it looks
like the pending massages cursor is a limitation for the receive side.
If you can produce wit
