Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of herve.barrault@gmail.com
 designates 209.85.213.171 as permitted sender)
MIME-Version: 1.0
Date: Mon, 13 Feb 2012 14:37:42 +0100
Message-ID: 
 <CAJUL34O6xreXTLmqjDwiA2dRsU-fTSQs2d3sVJ-LtUs6pdi0qA@mail.gmail.com>
Subject: Producer flow control
From: =?ISO-8859-1?Q?Herv=E9_BARRAULT?= <herve.barrault@gmail.com>
To: users <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=20cf301b685f33eec804b8d8954c

--20cf301b685f33eec804b8d8954c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

i have looked to the documentation of the producer flow control
functionality (http://activemq.apache.org/producer-flow-control.html).

I see that it is based on the storage size but in my case, i think not
being able to use the size.
I have a queue where i put messages two kind of messages : Big 10MB and
Small 1kB.

As Big messages are rare (compared to small ones), i would limit the Memory
to 100MB (10 messages).
But for small messages i would limit the number of small messages to 5000
(so about 5MB) . We have noted that with JDBC persistence, the number of
pending messages in the broker (not by queue) is important for
"performances".

As i would keep the order of Big and Small messages, i put them in the same
queue.

Is there a way to define a strategy for the flow control which is 100MB and
5k messages ?


Regards
Herv=E9

--20cf301b685f33eec804b8d8954c--