activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2401) Hangs in fan-in to DUPS_OK_ACKNOWLEDGE queue receivers
Date Wed, 23 Sep 2009 20:55:51 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hiram Chirino updated AMQ-2401:
-------------------------------

    Attachment: AMQ-2401.patch

Attaching patch which changes the DUPS_OK queue consumer behavior to match that of AUTO_ACK.
 The topic should still behave as before.

> Hangs in fan-in to DUPS_OK_ACKNOWLEDGE queue receivers
> ------------------------------------------------------
>
>                 Key: AMQ-2401
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2401
>             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: AMQ-2401.patch, 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.


Mime
View raw message