tent, this
> is expected as they share a resource, the consumer dispatch queue.
> Batching acks either using client ack mode or transactions helps
> reduce the overhead.
>
> If you have not yet tried a 5.6-SNAPSHOT, can you verify it behaves the
> same.
>
>
> On 13 Se
Hey Folks,
I tried the concurrentStoreAndDispatchQueues="false" and it didn't help. I
still see around 10X drop in producer throughput with backlog.
1 Queue , 8 producers, 2 consumers , No backlog : 1200 QPS (producer), 1200
QPS (consumer)
1 Queue, 8 Producer, 2 consumer, 4GB backlog (2M events)
if there is a real contention problem there.
> If you can generate a simple junit test case that demonstrates the
> behavior you are seeing, please open a jira issue and we can
> investigate some more.
> A test case will help focus the analysis.
>
> On 12 September 2011 01:08, b
Thanks,
I think I have disabled producer flow control in my config as
Is this sufficient or I nee
Hello folks,
I am evaluating ActiveMQ for some simple scenarios. The web-server will push
notifications to the queue/topic to be consumed by one or many consumers.
The one requirement is web-server should not get impacted or should be able
to write at their speed even if consumers goes down etc.
