Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 8 Jan 2015 15:45:35 +0000 (UTC)
From: "Jaewoong Choi (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12661495.1375481008000.38630.1420731935188@Atlassian.JIRA>
In-Reply-To: <JIRA.12661495.1375481008000@Atlassian.JIRA>
References: <JIRA.12661495.1375481008000@Atlassian.JIRA>
 <JIRA.12661495.1375481008898@arcas>
Subject: [jira] [Commented] (AMQ-4666) Topic persistent message publishing
 is blocked by hitting 100% of per-destination memory limit if there's any
 durable subscriber connected but not consuming.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269459#comment-14269459 ] 

Jaewoong Choi commented on AMQ-4666:
------------------------------------

Have you read the problem description section at #4 in my original request? In short, why would all "persistent" message publishing are blocked by topic's shared memory limit which is only for non-persistent messages, unnecessarily??  That's the problem. 

> Topic persistent message publishing is blocked by hitting 100% of per-destination memory limit if there's any durable subscriber connected but not consuming.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4666
>                 URL: https://issues.apache.org/jira/browse/AMQ-4666
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.7.0
>            Reporter: Jaewoong Choi
>         Attachments: MemoryLimitTest.java
>
>
> Failing scenario:
> 1. Embedded broker starts with the following configurations:
>    - persistent = true,
>    - systemUsage.memoryUsage.limit = 10*1024*1024 // 10mb broker main memory limit
>    - destinationPolicy.policyEntry.memoryLimit = 1*1024*1024 // 1mb per-destination memory limit
> 2. Create a topic durable subscription with prefetchLimit=0.
> 3. Create a topic publisher and publish persistent 400kb messages.
> 4. (Problem) After publishing 3 messages successfully, PFC kicks in and the above topic publisher gets blocked its publishing.
> At step #4, the expectation is not seeing any publisher blocking for the persistent message publishing until the store limit is reached.  How come the persistent message publishing is limited by 100% memory full?
> Per the code inspection, this is because the store cursor of the topic durable subscriber (i.e. TopicStorePrefetch) is working with the main broker's memory limit, not with the per-destination memory limit.  Hence, it keeps increasing broker main memory usage over the per-destination memory limit and after it reached 100% of per-destination limit, PFC kicked in.
> I verified that the above scenario went through well if I fix the store cursor to use/refer-to the per-destination memory usage along with its pending list (cache) management.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)