You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/10/25 17:14:58 UTC
[jira] [Commented] (AMQ-6481) Producer Flow Control not disabling
[ https://issues.apache.org/jira/browse/AMQ-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605890#comment-15605890 ]
Christopher L. Shannon commented on AMQ-6481:
---------------------------------------------
Were the destinations created after you configured the policy? Looking at your configuration, it should apply to new destinations and disable the flow control flag but it won't apply to any existing destinations that were created before disabling the flag in your policy. Also you can try the latest 5.14.x version as well to see if that makes any difference.
If you are still having an issue it would be a good idea to try and write a test case/junit test to demonstrate an issue if it exists.
> Producer Flow Control not disabling
> -----------------------------------
>
> Key: AMQ-6481
> URL: https://issues.apache.org/jira/browse/AMQ-6481
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.3
> Environment: Active MQ 5.13.3 in Karaf 4.x
> Camel 2.16.3
> Centos OS
> Reporter: Ranjit Nethi
>
> Producer flow control cannot be disabled in activemq 5.13.3. I have tried to disable producer flow control using the following configurations for destination policy and system usage below.
> I was able to recreate this issue easily by reducing the memory limit to very low value and send messages consistently (load test). Once the memory usage shows 100% on the activemq console. I can see the producer flow control kicks in with the following message in log:
> Usage Manager memory limit reached 134217728. Producers will be throttled to the rate at which messages are removed from this destination to prevent flooding it. See http://activemq.apache.org/producer-flow-control.html for more info.
> I can surely increase the memory limit, but that would only push the occurrence of the issue to later.
> <destinationPolicy>
> <policyMap>
> <policyEntries>
> <policyEntry topic=">" producerFlowControl="false">
> <dispatchPolicy>
> <strictOrderDispatchPolicy />
> </dispatchPolicy>
> <pendingSubscriberPolicy>
> <fileCursor />
> </pendingSubscriberPolicy>
> <pendingDurableSubscriberPolicy>
> <fileDurableSubscriberCursor />
> </pendingDurableSubscriberPolicy>
> </policyEntry>
> </policyEntries>
> <policyEntries>
> <policyEntry queue=">" producerFlowControl="false">
> <pendingQueuePolicy>
> <fileQueueCursor />
> </pendingQueuePolicy>
> </policyEntry>
> </policyEntries>
> </policyMap>
> </destinationPolicy>
> <systemUsage>
> <systemUsage>
> <memoryUsage>
> <memoryUsage limit="128 mb/>
> </memoryUsage>
> <storeUsage>
> <storeUsage limit="3 gb"/>
> </storeUsage>
> <tempUsage>
> <tempUsage limit="1 gb"/>
> </tempUsage>
> </systemUsage>
> </systemUsage>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)