You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jaume Teixi (JIRA)" <ji...@apache.org> on 2016/06/09 17:05:21 UTC
[jira] [Created] (AMQ-6318) policyEntry doesn't handle wildcards
properly
Jaume Teixi created AMQ-6318:
--------------------------------
Summary: policyEntry doesn't handle wildcards properly
Key: AMQ-6318
URL: https://issues.apache.org/jira/browse/AMQ-6318
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.13.3
Reporter: Jaume Teixi
Just trying to setup a policyEntry for a limit of pending messages in a topic "customer01.data.value" where an application is writing messages to just realized that the wildcards seems to not to being handled properly.
{code:xml}
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" >
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:
http://activemq.apache.org/slow-consumer-handling.html
-->
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>
<policyEntry topic="*.data.>" topicPrefetch="1" durableTopicPrefetch="1">
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="10"/>
</pendingMessageLimitStrategy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
{code}
Above causes inconsistencies on all the topics receiving messages that even didn't match the wildcard naming ie. "customer01.in.data"
Tried also with:
{code:xml}
<policyEntry topic="customer01.data.>" topicPrefetch="1" durableTopicPrefetch="1">
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="10"/>
</pendingMessageLimitStrategy>
</policyEntry>
{code}
and with:
{code:xml}
<policyEntry topic="customer01.data.value" topicPrefetch="1" durableTopicPrefetch="1">
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="10"/>
</pendingMessageLimitStrategy>
</policyEntry>
{code}
Last two above didn't caused inconsistencies on the topics that didn't match the naming but anyway didn't made the limit strategy of pending messages for the topic "customer01.data.value"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)