Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 74.125.82.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1150098585.2450.1340862032840.JavaMail.root@arise.pl>
References: <365941169.2364.1340861623673.JavaMail.root@arise.pl>
	<1150098585.2450.1340862032840.JavaMail.root@arise.pl>
Date: Thu, 28 Jun 2012 16:07:12 +0100
Message-ID: 
 <CAH+vQmM1LJzWkg4DQB1+LM5pHHKkp749_V5u5U9yXbPWOrM7HQ@mail.gmail.com>
Subject: Re: PFC + temp-queue
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

answers inline:

On 28 June 2012 06:40, Marcin Giedz <marcin.giedz@arise.pl> wrote:
>
> Hi,
>
>
> I was wondering why with temp-queue and producer flow control set to ON +=
 temp storage we still experience producers stop preventing flooding. Is th=
is a bug or a feature?
>
That is a feature. the cursor gets to consume all of the destination
limit and then the destination is considered full.
The filepending message cursor will only spool to disk with the
systemUsage limit is reached, up until that point it will keep
messages in memory like the vmpendingMessage cursor.

>
>
> <broker xmlns=3D"http://activemq.apache.org/schema/core" brokerName=3D"wa=
w1-amq1" dataDirectory=3D"${activemq.base}/waw-data" useJmx=3D"true" adviso=
rySupport=3D"true" persistent=3D"true" schedulePeriodForDestinationPurge=3D=
"10000" networkConnectorStartAsync=3D"true" allowTempAutoCreationOnSend=3D"=
true">
>
>
>
>
>
> <policyEntry tempQueue=3D"true" producerFlowControl=3D"true" memoryLimit=
=3D"100mb" gcInactiveDestinations=3D"true" inactiveTimoutBeforeGC=3D"60000"=
>
> <pendingQueuePolicy>
> <fileQueueCursor/>
> </pendingQueuePolicy>
> </policyEntry>
>
>
> ....
>
>
>
> <systemUsage>
> <systemUsage>
> <memoryUsage>
> <memoryUsage limit=3D"24 gb"/>
> </memoryUsage>
> <storeUsage>
> <storeUsage limit=3D"10 gb" name=3D"store"/>
> </storeUsage>
> <tempUsage>
> <tempUsage limit=3D"10 gb"/>
> </tempUsage>
> </systemUsage>
> </systemUsage>
>
>
> If I disable PFC on temp-queue I can see storage utilization once memory =
is exhousted but there is no any control over temp-queue. This behavour is =
common for 5.5.1 and 5.6.0. Should I file a bug or change my configuration?
>

With the destination limit removed, the system limit gets a chance to
be reached and the file cursor purges to temp storage. It is possible
to limit the temp store, and then the destination will block on a
send.


If key here is to understand that the spooling to disk with the file
pending message cursor is controlled by the shared systemUsage and not
the destination usage.

What behavior would you like to have?

>
> Thank you
> Marcin


--=20
http://fusesource.com
http://blog.garytully.com