johnbing==Anuj? same person posting all these under diff alias? funny shit....
so like i said, post your stack trace.. and also your config (broker + JVM args + client settings, etc), and we can help out more. NIO doesn't "reduce threads" magically in the overall broker... it reduces the number needed to sustain large numbers of connections. If you have other settings that create more threads in the broker core, then it's a wash right? On Fri, Sep 6, 2013 at 2:23 AM, johnbing <bingjoh...@gmail.com> wrote: > Yes I have also tested it with 20 producers consumers. But still not seeing > any reduction in the number of threads. I have tested NIO with STOMP as > well > as JMS producers. > > USING(Language) No. of threads before running producer No. of > threads after running producers(~20) > STOMP (PYTHON producer) 63 > 72 > STOMP +NIO(PYTHON producer) 67 > 82 > TCP(JAVA producer) 58 > 86 > NIO(JAVA producer) 58 > 87 > > Thanks, > Anuj > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/NIO-transport-performance-for-ActiveMQ-tp4670977p4671250.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
