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: No performance improvement using PooledConnectionFactory (AMQ 5.12.1).
Date Fri, 26 Feb 2016 13:54:57 GMT
It's also possible that 8 isn't the optimal pool size for your test driver,
and that a different (presumably larger) value would give better
throughput.  Tuning the pool size of any pooling technology (ActiveMQ,
JDBC, etc.) is an iterative and experimental process, and your first guess
often won't be the optimal one.
On Feb 25, 2016 9:26 PM, "artnaseef" <art@artnaseef.com> wrote:

> I agree with Robbie's comments here.  The statement that the application
> only
> creates the connections once got me confused at first, but looking at the
> original post, the pseudo-code there clearly creates the connection once on
> each producer.
>
> To verify, start up the application and use one of the following methods to
> check the number of actual connections to the broker:
>
> * ActiveMQ webconsole
> * netstat -an | grep 61616 | grep ESTABLISHED  # on the broker box
> * JConsole, VisualVM, or the like (view the connection mbeans, or the
> connection count on the broker mbean)
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/No-performance-improvement-using-PooledConnectionFactory-AMQ-5-12-1-tp4708033p4708432.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

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