That was my initial thought also, so we had already set prefetch limit = 1,
which i think is the lowest allowed value, to run our tests:
ActiveMQPrefetchPolicy prefetchPolicy = new ActiveMQPrefetchPolicy();
prefetchPolicy.setAll(1);
connectionFactory.setPrefetchPolicy(prefetchPolicy);
With a v
My guess is that this is because messages are sitting in the prefetch
buffer of consumers while they are being slow to consume their current
message, making those messages unavailable for other consumers who might be
idle.
If you change your consumers' prefetch size to 0, do you get the expected
t
Hello,
TLDR: When we introduce some latency on the consumers, the maximum consume
rate drops drastically, even though we have enough consumer threads to
handle the rate.
We are currently evaluating ActiveMQ, focusing on produce/consume rate:
The setup is the following:
- Virtual Topics: 100
- C
so they always end up in the same session. We
> did this by allowing amq.init() to accept a configuration option called
> sessionInitializedCallback. addListener calls go in this callback.
>
> We're just waiting on AMQ-2948 before submitting this patch.
>
> alex
>
>
>
--
On Oct 8, 2010, at 5:09 AM, jule wrote:
>
> I found a (quite obvious) solution to this problem. I just added a call to
> removeListener() of amq.js just before adding my listener on startup, like
> so:
>
> amq.removeListener(id, destination);
> amq.addListener(id, destination, callBack);
>
> N
seen other results. What kind of test did you do?
>
>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Beginner-problem-Too-many-consumers-on-queue-after-browser-restart-tp2719286p2968092.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
parameter will be ignored,
the problem persists. And for my application a refresh after the browser
restart won´t work. It remains broken with too many consumers on the queue.
I tried to apply the patch that you posted but unfortunately I can´t get it
to work: I downloaded the 5.4.1 sources, did
without a reload thereafter) and
messaging remained functioning.
I will do some additional tests of my application tomorrow and will post if
this still works for me then (which would be quite misterious if this
parameter will be ignored in the current implementation ;-)).
--
View this message in co
On Sep 30, 2010, at 4:33 PM, jule wrote:
>
> Hi Alex,
>
> you´re right, reloading after restart will get it back to work. Thanks for
> your explanation. Is there a schedule for the patch you mentioned?
Our plan (at my work) is to get
https://issues.apache.org/activemq/browse/AMQ-2948 accepted
The broker in the middle allows my clients
(mobiles) behind NAT/PAT to be reachable (push via ActiveMQ HTTP long-poll).
I am very content with this now.
Best regards
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Beginner-problem-Too-many-consumers-on-queue-after-brows
On Sep 30, 2010, at 10:51 AM, jule wrote:
>
> I just found out that this behaviour can also be reproduced with the
> "chat"-example with an out-of-the-box configured ActiveMQ broker. If a
> client browser is restarted, this example app breaks and the client cannot
> receive anymore.
If you rest
2283324.n4.nabble.com/Beginner-problem-Too-many-consumers-on-queue-after-browser-restart-tp2719286p2721032.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ing and supporting ActiveMQ, I am really amazed of how fast
the long poll technique for web-clients works.
Best regards
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Beginner-problem-Too-many-consumers-on-queue-after-browser-restart-tp2719286p2719286.html
Sent from the
sage in context:
http://activemq.2283324.n4.nabble.com/Newbie-question-about-many-consumers-and-many-producers-tp2402003p2402091.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
this message in context:
http://activemq.2283324.n4.nabble.com/Newbie-question-about-many-consumers-and-many-producers-tp2402003p2402090.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ason you would not consider using separate queues for
>each of the different consumers? Seems that it may simplify your solution.
>
>Matt Pavlovich
>
>On Aug 31, 2010, at 12:30 PM, ChicagoBob123 <[hidden email]> wrote:
>
> >
> > Newbie question about many consumers
Am 31.08.2010 19:30, ChicagoBob123 wrote:
The messages contain ID's for consumers of the messages to
know to it is their message/task.
If the IDs are set as message properties, the client can filter their
own messages by using a selector on the messageconsumer.
I tried to only acknowledge
Is there a reason you would not consider using separate queues for each of the
different consumers? Seems that it may simplify your solution.
Matt Pavlovich
On Aug 31, 2010, at 12:30 PM, ChicagoBob123 wrote:
>
> Newbie question about many consumers and many producers.
> I have
Newbie question about many consumers and many producers.
I have searched and read through some of the archives but have not been able
to find an answer to this question.
I am working on an application that will have several different producers.
They supply messages to
a common queue. The
On 9/12/07, Sean Folster <[EMAIL PROTECTED]> wrote:
> how do I configure broker(s) so that it receives message on specific topics
> and then sends them to all consumers persistently
The default out-of-the-box ActiveMQ does that.
http://activemq.apache.org/how-do-i-get-started-with-jms.html
http:
how do I configure broker(s) so that it receives message on specific topics and
then sends them to all consumers persistently
-
Check out the hottest 2008 models today at Yahoo! Autos.
21 matches
Mail list logo
