Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 akarpe@fusesource.com does not designate 216.139.236.26 as permitted sender)
Date: Tue, 12 Apr 2011 05:06:59 -0700 (PDT)
From: Ashwin Karpe <akarpe@fusesource.com>
To: users@camel.apache.org
Message-ID: <1302610019202-4298040.post@n5.nabble.com>
In-Reply-To: <1302603452703-4297889.post@n5.nabble.com>
References: <1302603452703-4297889.post@n5.nabble.com>
Subject: Re: Multiple message producers and consumers per ActiveMQ session
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

The short answer is yes. It is thread safe. As for performant, it is more
nuanced. If you have multitple threads reusing the same session/connection,
you could get contention for the connection object. For performance, you may
be better off using a PooledConnectionFactory. I would also advise that you
set the consumer.prefetchSize on the Connection object to 1 in order to not
lock up a lot of memory in the connection objects.

This is very do-able in Camel by setting up the right kind of
ConnectionFactory for the JMS or ActiveMQ component.
Hope this helps. 

Cheers,

Ashwin...

-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com 

Blog: http://opensourceknowledge.blogspot.com 
CamelOne 2011: http://fusesource.com/camel2011 
---------------------------------------------------------
--
View this message in context: http://camel.465427.n5.nabble.com/Multiple-message-producers-and-consumers-per-ActiveMQ-session-tp4297889p4298040.html
Sent from the Camel - Users mailing list archive at Nabble.com.