Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B4D5A100D9 for ; Thu, 25 Jul 2013 18:07:34 +0000 (UTC) Received: (qmail 55831 invoked by uid 500); 25 Jul 2013 18:07:34 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 55798 invoked by uid 500); 25 Jul 2013 18:07:33 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 55790 invoked by uid 99); 25 Jul 2013 18:07:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 18:07:33 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of christian.posta@gmail.com designates 209.85.215.49 as permitted sender) Received: from [209.85.215.49] (HELO mail-la0-f49.google.com) (209.85.215.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 18:07:27 +0000 Received: by mail-la0-f49.google.com with SMTP id ea20so1610933lab.36 for ; Thu, 25 Jul 2013 11:07:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=rbgtRjt1u9o99XQrbiyXTpbnoBkAxsIV0/xO4X9+/zg=; b=ccmFTHDcbtKryFHIW1YoaqfKHVupoAc6DCR+VszshtS3TjqPhtRIla7S00OijlFUBc 9HSC3xSY+uZHpZEzuCU9jUHTYLHQV9pv2A5KezEMY+tqKdn/tJ4TVOXue6AAAohzS3fY cs1zw2jaRlhSzw8aGZAfIdKT4MSo+kt5iFN8NHt1CFIT/rkLDq6P0d0uSvsjL4kkWago vIpJNgLyOAq9oNqns19IbGLQoAG1gphXiihIvfcbCFSfoZczUnUnwMpKUW2ODOqC4WaR MsGKAzfBoOVgOAkCKX0Mf9T7iygOnpyAOPkLZQc6RwMwtWFWws74jkkrkSHYgJmTXfZf MI6g== MIME-Version: 1.0 X-Received: by 10.112.159.169 with SMTP id xd9mr18989385lbb.43.1374775627250; Thu, 25 Jul 2013 11:07:07 -0700 (PDT) Received: by 10.114.2.239 with HTTP; Thu, 25 Jul 2013 11:07:07 -0700 (PDT) In-Reply-To: <1374680070156-4669679.post@n4.nabble.com> References: <1374680070156-4669679.post@n4.nabble.com> Date: Thu, 25 Jul 2013 14:07:07 -0400 Message-ID: Subject: Re: cursor memory usage/limit vs memory usage/limit From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=001a11c3cdbae8839704e259e444 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3cdbae8839704e259e444 Content-Type: text/plain; charset=ISO-8859-1 I have written a little about this.. maybe check out: http://www.christianposta.com/blog/?p=273 On Wed, Jul 24, 2013 at 11:34 AM, Jake Choi wrote: > Hi, > > Using activemq-core-5.7.0 (embedded broker), I noticed that there is the > separate memory usage/limit called "cursor memory usage/limit" which the > per-destination memory limit (that I set via per-destination policy) > doesn't > account for, but shared between all queues. For example, from the JMX > stats, I see all queues show the same values for the "Cursor*" metrics > while > independent stats for "Memory*" stats: the following is the JMX stat of one > of queues: > > # the following 3 are all the same between queues > "CursorMemoryUsage": 4294967698, > "CursorPercentUsage": 100, > "CursorFull": true, > > # the following 3 are all different between queues > "MemoryLimit" : 536870912, > "MemoryPercentUsage" : 0, > "MemoryUsagePortion" : 0, > > I confirmed that this was not just stat difference but actually the queue > above got affected such that it's producers got blocked by hitting this > "cursor memory limit" to which usage it hasn't contributed at all, even > though it doesn't use any memory (MemoryPercentUsage: 0). > > So, here're some questions: > 1) what's the difference between these two memory areas: > cursor-memory-usage > and (just) memory-usage. when/who uses which? > 2) can I configure per-destination limit to this cursor-memory-usage as > well? > > Thanks! > Jaewoong > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/cursor-memory-usage-limit-vs-memory-usage-limit-tp4669679.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta --001a11c3cdbae8839704e259e444--