I went back to 5.1 and this behavior seems to work well by default with the
KahaPersistenceAdapter. I assume it is using the Store Based Cursor. I
didn't configure a PolicyEntry. Memory usage is capped at 64MB, which is
the default cap. I will use 5.1 as my work around for now.
scot
hment/18932/UnlimitedEnqueueTest.java
>
>
> On 16 February 2010 11:38, Gary Tully wrote:
>
>> There is something not right here. let me build a test case to
>> investigate
>> a bit.
>>
>>
>> On 16 February 2010 01:19, scot.hale wrote:
>>
>>
he system usage so no spooling to disk occurs.
>
> 2) Configure a SystemUsage.MemoryLimit that is less than the default
> destination memory limit of 64M
>brokerService.getSystemUsage().getMemoryUsage().setLimit(1024 * 1024 *
> 63);
>
> This should do it once you add a TempStore(
t; Hi Scott,
>
> just change the below config to enable flow control - i.e:
>
>
>
>
> in 5.3 - producerFlowControl is on by default - so just remove the
> producerFlowControl entry from your configuration.
>
> If this all sounds double dutch - send in you
Fred,
Were you able to configure ActiveMQ to grow without surpassing the memory
setting? I am trying to figure out how to do the same thing.
-Scot
Fred Moore-3 wrote:
>
> Hi,
>
> going back to Cursors and
> http://activemq.apache.org/how-do-i-configure-activemq-to-hold-100s-of-millions-of-
