Return-Path: 
 <users-return-10043-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 2813 invoked from network); 30 Nov 2009 21:45:30 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 30 Nov 2009 21:45:30 -0000
Received: (qmail 37529 invoked by uid 500); 30 Nov 2009 21:45:30 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 37502 invoked by uid 500); 30 Nov 2009 21:45:30 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 37492 invoked by uid 99); 30 Nov 2009 21:45:30 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Nov 2009 21:45:30 +0000
X-ASF-Spam-Status: No, hits=1.4 required=10.0
	tests=FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.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, 30 Nov 2009 21:45:20 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1NFE3H-0008U1-Ka
	for users@camel.apache.org; Mon, 30 Nov 2009 13:44:59 -0800
Message-ID: <26582486.post@talk.nabble.com>
Date: Mon, 30 Nov 2009 13:44:59 -0800 (PST)
From: skt99 <sk_telang@yahoo.com>
To: users@camel.apache.org
Subject: Re: concurrentconsumers thread safe?
In-Reply-To: <26582427.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: sk_telang@yahoo.com
References: <26582427.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org


It appears my configuration did not get copied properly..I am sending it
again...thanks.

  <camel:camelContext id="camelContext">
        <camel:route id="response">
            <camel:from uri="jms:queue:dev.callback.Response"/>
            <camel:to uri="bean:asyncMDPCallback"/>
        </camel:route>
    </camel:camelContext>

 <bean id="workflowflowExceptionTaskExecutor"
         
class="org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor">
        <property name="corePoolSize" value="5"/>
        <property name="maxPoolSize" value="10"/>
        <property name="queueCapacity" value="25"/>
</bean>

 <bean id="jmsConfig"
class="org.apache.camel.component.jms.JmsConfiguration">
        <property name="connectionFactory"
ref="jcaPooledConnectionFactory"/>
        <property name="transactionManager" ref="transactionManager"/>
        <property name="transacted" value="true"/>
        <property name="taskExecutor" ref="workflowCallbackTaskExecutor"/>
        <property name="concurrentConsumers" value="5"/>
        <property name="maxConcurrentConsumers" value="10" />     
    </bean>

 <bean id="jms"
class="org.apache.activemq.camel.component.ActiveMQComponent">
        <property name="configuration" ref="jmsConfig"/>      
 </bean>

Appreciate any help.


skt99 wrote:
> 
> Hi,
>    I have this configuration - The Spring context is loaded only once on
> app startup. An MDP asyncMDPCallback configured as a singleton using
> Spring, is setup to consume messages.
> 
>   <camel:camelContext id="camelContext">
>         <camel:route id="response">
>             <camel:from uri="jms:queue:dev.callback.Response" />
>             <camel:to uri="bean:asyncMDPCallback" />
>         </camel:route>
>     </camel:camelContext>
> 
>  <bean id="workflowflowExceptionTaskExecutor"
> class="org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor">
>         <property name="corePoolSize" value="5" />
>         <property name="maxPoolSize" value="10" />
>         <property name="queueCapacity" value="25" />
> </bean>
> 
>  <bean id="jmsConfig"
> class="org.apache.camel.component.jms.JmsConfiguration">
>         <property name="connectionFactory"
> ref="jcaPooledConnectionFactory" />
>         <property name="transactionManager" ref="transactionManager" />
>         <property name="transacted" value="true" />
>         <property name="taskExecutor" ref="workflowCallbackTaskExecutor"
> />
>         <property name="concurrentConsumers" value="5" />
>         <property name="maxConcurrentConsumers" value="10" />     
>     </bean>
> 
>  <bean id="jms"
> class="org.apache.activemq.camel.component.ActiveMQComponent">
>         <property name="configuration" ref="jmsConfig" />      
>  </bean>
> 
> Is this setup for concurrentConsumers using ThreadPoolTaskExecutor
> thread-safe by default, or do I need to handle it in my app? Appreciate
> any help.
> 

-- 
View this message in context: http://old.nabble.com/concurrentconsumers-thread-safe--tp26582427p26582486.html
Sent from the Camel - Users mailing list archive at Nabble.com.