No one have any ideas on this? I was thinking that I could up the max connections to something higher and then setting the maximum number of active sessions per connection on the PooledConnectionFactory. I don't really like this solution though as it leads to an issue when you hit that max.
On 30/01/2014 23:06, "Joshua Watkins" <joshua.watk...@gamesys.co.uk> wrote: > >I am looking for a bit of advice. I have been trying to get a better >balance of consumer per connection but have run into a bit of a sticky >situation. > >So while using the AMQ 5.8 and the AMQ PooledConnectionFactory[1], I was >setting my camel routes with Cache_None to enable more connections from >the pool to be used. In addition to that I am using DMLC session >transactions to ensure messages are properly consumed.[2] Unfortunately >this has the side effect of spamming the Consumer advisory topics because >consumers are only used after consuming a single message. Is there an >easier way to get a better consumer distribution on connections without >this side effect? > > >Thanks, >Josh > > > >1. PooledConnectionFactory config: ><bean id="connectionFactory" >class="org.apache.activemq.pool.PooledConnectionFactory" >init-method="start" destroy-method="stop"> > <constructor-arg ref="amqConnectionFactory" /> > <property name="maxConnections" value="10" /> > <property name="idleTimeout" value="0"/> (0 to deal with > AMQ-4366) > </bean> > > > >2. Camel config: >cacheLevelName=CACHE_NONE >transacted=true >lazyCreateTransactionManager=false >replyToDeliveryPersistent=false >acknowledgementModeName=CLIENT_ACKNOWLEDGE > > >
