Issue

• Could you confirm the expected behaviour of the org.apache.activemq.pool.PooledConnectionFactory with regards to connection creation; is it lazy, greedy or something else? We have connection pooling setup (spring context attached) that is used by our Camel routes to connect to an ActiveMQ broker and consume messages. It appears that on (or very near) startup the pool creates "maxConnections" new connections regardless of whether they are required by our Camel routes or not.
  Based on this observation it appears that the PooledConnectionFactory greedily creates all the permitted connections up front. Is this the expected behaviour and is it possible to configure the pool to lazily create new JMS connections as they are required.