I was reading some old discussion threads on connection pooling. There seems to be some conflicting information, specifically whether it's a good idea to pool connections.
I have been using the jencks-amqpool package for pooling connections (and also trying the pool package within activemq-core). In looking at this article: http://www.nabble.com/Configuring-session-connection-pooling-to-maximize-throughput-to8177244s2354.html#a8177244 It states: "However one area to be careful of is currently each connection's commands are processed by a single thread on the broker side; so for relatively slow operations like durable producers you won't get much concurrency on the broker side (Guillaume hit this recently AFAIK on ServiceMix). So you might want to have many connections too so that you can have completely async broker side processing of separate producers. Though we should allow a thread pool to be used for different logical sessions on the broker side to avoid the client having to worry about that. " This is why I've been using the connection pooling stuff. Is this still an issue in amq 5, is the broker still single-threaded when processing each connection? Also, I've been using Spring's JmsTemplate for sending, and DefaultMessageListenerContainer for consuming messages (in both cases using a PooledConnectionFactory for connections)....Is this a recommended approach? The Spring api's seemed a whole lot cleaner than the activemq-ra/jencks MDB POJO stuff.... Jason -- View this message in context: http://www.nabble.com/Broker-concurrency-and-connection-pooling-in-amq-5-tp15328732s2354p15328732.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
