You should use CACHE_CONSUMER if you can. Its much faster. Though some brokers and TX managers does not support it, and thus rely on CACHE_NONE. Especially if you use XA transactions.
For single resource transaction with only ActiveMQ then using CACHE_CONSUMER is safe and supported. And its much faster. On Sun, Jun 2, 2013 at 3:12 PM, Darwish <othman.darw...@progressoft.com> wrote: > Hi, > > im using transacted route which consuming exchanges from JMS component ( > ActiveMQ ) and follow recommended setting as mentioned in > http://camel.apache.org/jms.html .I setup cacheLevelName to CACHE_NONE , the > result is thousands of TIME_WAIT connections crated and approaching the > maximum OS (Windows) ports limit !! > > im using camel 2.11 with AMQ 5.8 > > any Help ? > > > > > > > <bean id="Activemq" > class="org.apache.activemq.camel.component.ActiveMQComponent"> > <property name="connectionFactory"> > <bean > class="org.apache.activemq.ActiveMQConnectionFactory"> > <property name="brokerURL" > value="tcp://10.3.150.132:61001?jms.redeliveryPolicy.maximumRedeliveries=0" > /> > <property name="userName" value="system" /> > <property name="password" value="manager" /> > </bean> > </property> > <property name="transacted" value="true" /> > <property name="transactionManager" ref="transactionManager" > /> > <property name="receiveTimeout" value="250" /> > <property name="cacheLevelName" value="CACHE_NONE" /> > </bean> > > > > > > > > > > ----- > Othman Darwish > ProgressSoft Corp. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Transactions-and-Cache-Levels-tp5733618.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
