activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin MacNaughton (JIRA)" <>
Subject [jira] Commented: (AMQ-2401) Hangs in fan-in to DUPS_OK_ACKNOWLEDGE queue receivers
Date Tue, 22 Sep 2009 21:02:56 GMT


Colin MacNaughton commented on AMQ-2401:

After some changes committed by Rob and Dejan in 5.4 trunk, the 50_1_1 usecase is better than
before. However, setting the pending queue policy to vm results in the old buggy behavior,
which is problematic for those thar don't wish to page messages to disk:

{code:title=Modify setup to include vm pending cursor,java}
entry.setPendingQueuePolicy(new VMPendingQueueMessageStoragePolicy());

> Hangs in fan-in to DUPS_OK_ACKNOWLEDGE queue receivers
> ------------------------------------------------------
>                 Key: AMQ-2401
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>         Environment: Running with the following config:
> <destinationPolicy>
>  <policyMap>
>    <policyEntries>
>      <policyEntry topic=">" producerFlowControl="true" memoryLimit="1mb">  
>        <pendingSubscriberPolicy>
>          <vmCursor/>
>        </pendingSubscriberPolicy>
>      </policyEntry>
>      <policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb"/>
>    </policyEntries>
>  </policyMap>
> </destinationPolicy>
>            Reporter: Colin MacNaughton
>         Attachments: AMQ2401.txt
> While running performance tests I I was seeing hangs in several tests  involving dups
ok queue receivers. My suspicion is that this is related to "too lazy" dups_ok acknowledgements.
Changing the queue prefetchLimit to 100 caused this problem to go away. This needs more investigation,
but it seems like we can get ourselves in to trouble if the queue size is smaller than the
receiver's prefetchLimit, and this should be avoid. It is also possible that there is something
more complicated happening in my tests. I haven't yet been able to reproduce this outside
my performance test environment. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message