activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Active MQ - Performance with CLIENT Ack
Date Sat, 15 Jul 2017 04:20:54 GMT
Is your workflow process-ack-process-ack-process-ack (one message at a time
immediately followed by acking that one message, in a single thread)? If
so, I'd expect your processing to be slower than if you only acknowledge
every Nth message, though I'm not sure how significant of a performance
impact I'd expect that to be.

Can you describe in more detail what you're actually observing? Are you
slowly but correctly consuming messages (i.e. this is a performance problem
but not a correctness problem)? Or is the problem that messages are not
being acknowledged at all (none, zip, zero), which makes this a correctness
problem? You've described both types of problem in your description, but
any problem is by definition only one or the other, and knowing what the
actual problem is will help us focus on what's actually wrong.

Tim

On Fri, Jul 14, 2017 at 6:54 PM, akpuvvada <akp4tibco@gmail.com> wrote:

> We are testing it from Tibco Business Works. We configured the JMS
> Connection
> using JNDI.
>
> With auto acknowledged we did not see any issues. Everything worked fine.
>
> We are testing queues. Topics are also in scope for the testing, have not
> started yet.
>
> I did not configure prefetch, using the default which as per documentation
> is 1000.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-Performance-with-CLIENT-Ack-tp4728551p4728566.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message