Yep, for 2, 3, 4, ... (i.e., smaller than producer produces ahead); for 1 it
doesn't work. In my test there's a constant at the beginning of a class,
currently 2. Changing to 1 breaks the test.
- Art
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Does it work for prefetchSize=2, just not 1? (Sorry, I won't be able to try
running the code till sometime next week, otherwise I'd just try it myself
rather than ask.)
Tim
On Thu, Aug 31, 2017 at 7:40 AM, art.licis wrote:
> I'm sorry, I sent a wrong link; Unit test is here:
> https://github.co
I'm sorry, I sent a wrong link; Unit test is here:
https://github.com/art-licis/activemq-jmx-monitor/blob/master/src/test/java/today/jvm/amq/ActiveMQJmxMonitorTest.java
If you need a completely independent unit test, that's possible.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-
Thanks Tim for youe feedback!
I'm using JDBC persistence adapter, storing the messages in PostgreSQL.
I'm using GroupID for ordering the messages withing the group. So, adding
more consumers does not help if message burst is from couple of groups.
I'm using memoryUsage setting to limit the memor
I've never seen any code that responds to slow consumers like that. There
are a few plugins that allow you to abort (i.e. disconnect) slow consumers,
but you have to enable them explicitly and you'd see logging about how the
broker was aborting them.
Are you using a persistence store, or just sto
there are two different Strategies
On 8 April 2014 11:19, khandelwalanuj wrote:
> Hi,
>
> I was going through https://issues.apache.org/jira/browse/AMQ-4621
> *(AbortSlowAckConsumerStrategy )*
>
> If I specify this strategy to abort slow consumers in my xml configuration,
> does it also changes t
Thanks Dejan
At what point is a Slow Consumer considered Slow is it configurable. I've tried
looking through the website and my copy of ActiveMQ in action but I can't find
anything specific about this.
Many Thanks
Mike
On 14 Jan 2011, at 12:59, Dejan Bosanac wrote:
> Hi Mike,
>
> you shoul
Hi Mike,
you should see ActiveMQ.Advisory.SlowConsumer.x topics, but only when
the first advisory of the kind is sent.
Regards
--
Dejan Bosanac
-
FuseSource - The experts in open source integration and messaging.
Email: dej...@fusesource.com
Web: http://fusesource.com
Twitter: ht
temporary destinations add additional overhead because to be compliant
with the JMS specification, a messaging system needs to validate that
the temporary destination exists before sending every message. To
avoid slowing delivery of messages to a crawl to a temporary queue,
ActiveMQ sends a
Yeah... by reusing the same temporary queues, the problem goes away. (We used
1 temp queue per request because the requests were originated at different
threads. We changed to use a fixed set of temp queues, listeners, and local
dispatching to work around.)
But this seems just fix the symptoms. I
You should not create the session and temporary queue for every request. You
should create them when you create the client [1] (or at least cache them).
These operations are expensive and require remote calls to the broker.
The slowdown of faster clients may be due to Producer Flow Control [2],
w
The same problem exists on 5.3 SNAPSHOT. Using the original configuration,
ActiveMQ printed out "WARN Usage - Memory usage is now at 100%". But
changing the configurations to
and
do not help. The same
Thanks. Will try.
More detail about the client is that when we send a queue request, we do
- create a Session
- create a TemporaryQueue
I wonder if these two will be broadcasting something to the other clients
and cause the backlog. Shouldn't be, but...
rajdavies wrote:
>
> Does this behavi
Does this behaviour change if you use the latest snapshot ?
thanks,
Rob
On 20 Jul 2009, at 03:51, mquestioner wrote:
Hi,
We have a case where a consumer connected through a slow connection
would
slow down the fast consumer. I have already
http://activemq.apache.org/slow-consumers.html and
any help on this would be greatly appreciated... =)
srasul wrote:
>
> Hi,
>
> when dealing with slow/deadlocked consumers, it seems that one thing that
> really helps is setting the MaximumPendingQueueSize in the subscription
> via JMX Console.
>
> My questions are: what is the difference bet
15 matches
Mail list logo