On Wed, Apr 7, 2010 at 10:56 PM, mattcodes <m...@mattfreeman.co.uk> wrote: > > The .Net library does not have a pooled connection factory. I will look at > porting the Java one. > > ...Yikes, I think I'll drop that idea, the naming is already making it not > suitable for hangover day. ConnectionPool represents a connection and > associated pool, not a connection pool.
There is a CachingConnectionFactory in the Spring .NET APIs: http://springframework.net/docs/1.3.0/api/net-2.0/html/topic17141.html I believe that the implementation in Spring .NET is nearly the same as the one in the Spring Java APIs. But I'm not a Windows/.NET type so I've CC'd Mark Pollack who created and maintains Spring .NET. > 1 to 1 for producer to session, and then shared connection(s). From what I > read things will be multiplexed onto the connection, is there anything on > the broker side to see the usage of a connection - how much its maxed out > by? thus providing a indicator of when to bring in multiple connections Various aspects of ActiveMQ can be monitored through JMX and jconsole will provide resource utilization monitoring. The best thing to do is test it in your environment (i.e., on your machines with your destinations, with your anticipated load, etc.) and watch the broker memory usage. The memory available to the broker can be adjusted via the <systemUsage> element in the activemq.xml. More info about it is available here: http://activemq.apache.org/producer-flow-control.html#ProducerFlowControl-Systemusage Bruce -- perl -e 'print unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
