Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 6169 invoked from network); 19 Jan 2009 06:18:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jan 2009 06:18:29 -0000 Received: (qmail 37628 invoked by uid 500); 19 Jan 2009 06:18:28 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 37611 invoked by uid 500); 19 Jan 2009 06:18:28 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 37600 invoked by uid 500); 19 Jan 2009 06:18:28 -0000 Delivered-To: apmail-activemq-camel-user@activemq.apache.org Received: (qmail 37597 invoked by uid 99); 19 Jan 2009 06:18:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Jan 2009 22:18:28 -0800 X-ASF-Spam-Status: No, hits=4.8 required=10.0 tests=DNS_FROM_OPENWHOIS,HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Jan 2009 06:18:21 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LOnSS-0003Hw-G9 for camel-user@activemq.apache.org; Sun, 18 Jan 2009 22:18:00 -0800 Message-ID: <21537495.post@talk.nabble.com> Date: Sun, 18 Jan 2009 22:18:00 -0800 (PST) From: huntc To: camel-user@activemq.apache.org Subject: Re: Unexpected ActiveMQ FailoverTransport messages in my log In-Reply-To: <21537172.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_70628_24087695.1232345880494" X-Nabble-From: huntc@mac.com References: <21512906.post@talk.nabble.com> <21514442.post@talk.nabble.com> <21515595.post@talk.nabble.com> <21537172.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_70628_24087695.1232345880494 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit OK - now I remember.. you have to use a pooled connection factory when producing to a queue as per: http://activemq.apache.org/jmstemplate-gotchas.html The crazy thing is that I knew that, but I had just forgotten. Given that my Camel application both produces and consumes on queues I have now created two connection components: <!-- Set up ActiveMQ --> <bean id="activemq-receiver" class="org.apache.activemq.camel.component.ActiveMQComponent"> <property name="connectionFactory"> <bean class="org.apache.activemq.ActiveMQConnectionFactory"> <property name="brokerURL" value="${mybrokerurl}" /> </bean> </property> </bean> <bean id="activemq-sender" class="org.apache.activemq.camel.component.ActiveMQComponent"> <property name="connectionFactory"> <bean class="org.apache.activemq.pool.PooledConnectionFactory"> <constructor-arg value="${mybrokerurl}" /> </bean> </property> </bean> I hope that this thread is a useful reminder for what would probably be a common trap. Would this be worth being included on the ActiveMQ component page? http://activemq.apache.org/camel/activemq.html Kind regards, Christopher -- View this message in context: http://www.nabble.com/Unexpected-ActiveMQ-FailoverTransport-messages-in-my-log-tp21512906s22882p21537495.html Sent from the Camel - Users mailing list archive at Nabble.com. ------=_Part_70628_24087695.1232345880494--