You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/03/08 17:46:40 UTC
[jira] [Commented] (AMQ-6199) cursorMemoryHighWaterMark
configuration not applied to topic subscription
[ https://issues.apache.org/jira/browse/AMQ-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185201#comment-15185201 ]
ASF subversion and git services commented on AMQ-6199:
------------------------------------------------------
Commit 078f39f5896ab728046424017f9cd4f45d53f48c in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=078f39f ]
https://issues.apache.org/jira/browse/AMQ-6199 - apply CursorMemoryHighWaterMark to topic subscriptions
> cursorMemoryHighWaterMark configuration not applied to topic subscription
> -------------------------------------------------------------------------
>
> Key: AMQ-6199
> URL: https://issues.apache.org/jira/browse/AMQ-6199
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.14.0
>
>
> One can configure
> {code:xml}
> <policyEntry topic=">" cursorMemoryHighWaterMark="10" />
> {code}
> but that cursorMemoryHighWaterMark is not set on the effective TopicSubscription. As a result, topic messages don't get swapped to disk once the explicitly configured water mark is reached.
> That should be a usage percentage of the systemUsage memory usage limit, but it stays at the default 70 in error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)