Hi Jochen Could I suggest maybe looking at the test cases how they're using it and see what maybe different in your code?
In particular look at testConnectionsArePooled https://github.com/apache/activemq/blob/master/activemq-jms-pool/src/test/java/org/apache/activemq/jms/pool/PooledConnectionFactoryTest.java Cheers Mike Sent from my iPhone > On 4 Jul 2017, at 06:17, jochenw <jochen.walz.m...@googlemail.com> wrote: > > Hi Mike, > > thanks for the answer. Of course I have checked this . It says: "A JMS > provider which pools Connection, Session and MessageProducer instances so it > can be used with tools like Camel and Spring's JmsTemplate and > MessagListenerContainer. Connections, sessions and producers are returned to > a pool after use so that they can be reused later without having to undergo > the cost of creating them again." > > However, I can see the log entries "Successfully connected to > tcp://0.0.0.0:61616" all the time - I would have expected that when the > first connections have been created, they are reused from the pool, and > there will be no more messages in the log file that a connection to the > broker has been made. > > Cheers, > Jochen > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/PooledConnectionFactory-createConnection-results-in-log-entry-Successfully-connected-to-tp4728188p4728195.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
