activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <>
Subject Re: NIO transport performance for ActiveMQ
Date Mon, 23 Sep 2013 13:44:04 GMT
I'm not seeing any issues with the previous thread usage.

ActiveMQ will use a pool of threads to handle the sockets for NIO, it won't
necessarily use a thread per socket.

As I said previously, and still maintain, please post *stack traces* or
analysis of thread usage for large numbers of connections and *show* that
you're not getting better thread usage *for connections*. It doesn't make
sense to use NIO and expect KahaDB threads to reduce.

On Mon, Sep 23, 2013 at 2:01 AM, Steven Turner <>wrote:

> Hey ceposta,
> Why nio reduces number of threads for large number of connections and not
> for small number, I think major advantage of nio transport is that it does
> not create one thread per connection as TCP does. So i think even if there
> are 5 clients it should reduce number of threads.
> Another thing is even if it reduces clients with large number, can you
> please specific about numbers, After how many clients we can see the
> significant thread reduction.
> Thanks,
> Steven
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

*Christian Posta*
twitter: @christianposta

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