Return-Path: 
 <camel-user-return-4838-apmail-activemq-camel-user-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org
Received: (qmail 56670 invoked from network); 16 Dec 2008 15:39:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 16 Dec 2008 15:39:44 -0000
Received: (qmail 40421 invoked by uid 500); 16 Dec 2008 15:39:56 -0000
Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org
Received: (qmail 40409 invoked by uid 500); 16 Dec 2008 15:39:56 -0000
Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:camel-user-help@activemq.apache.org>
List-Unsubscribe: <mailto:camel-user-unsubscribe@activemq.apache.org>
List-Post: <mailto:camel-user@activemq.apache.org>
List-Id: <camel-user.activemq.apache.org>
Reply-To: camel-user@activemq.apache.org
Delivered-To: mailing list camel-user@activemq.apache.org
Received: (qmail 40398 invoked by uid 99); 16 Dec 2008 15:39:56 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Dec 2008 07:39:56 -0800
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
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; Tue, 16 Dec 2008 15:39:42 +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 1LCc13-0003Rb-6T
	for camel-user@activemq.apache.org; Tue, 16 Dec 2008 07:39:21 -0800
Message-ID: <21035441.post@talk.nabble.com>
Date: Tue, 16 Dec 2008 07:39:21 -0800 (PST)
From: dougly <dmly.usa@gmail.com>
To: camel-user@activemq.apache.org
Subject: Re: Multiple Running Context
In-Reply-To: <5380c69c0812152107laec0dd2o338807d210e804c0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: dmly.usa@gmail.com
References: <21022918.post@talk.nabble.com>
 <5380c69c0812152107laec0dd2o338807d210e804c0@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Hi Claus,

I just tested the routes in our apps.
Even with two separate running contexts I am able to see messages flowing
between them! Whether this is a actual camel issue or jconsole issue (or
even possibly, the MBean part of Camel issue) I don't know.

Thanks

Doug


Claus Ibsen-2 wrote:
> 
> Hi
> 
> I guess you might have found an issue there, or at least in the jconsole.
> 
> Does the endpoints/consumers etc. work, but it's only the jconsole not
> showing the correct picture?
> I guess we need some unit tests with multiple context in the same
> spring xml file.
> 
> 
> 
> On Mon, Dec 15, 2008 at 11:04 PM, dougly <dmly.usa@gmail.com> wrote:
>>
>> Hi riders,
>> Is Camel 1.5 supporting multiple running context? I am trying to setup
>> two
>> contexts in the same web application and it's not functioning properly.
>> Here is the config:
>>
>> <camelContext xmlns="http://activemq.apache.org/camel/schema/spring"
>> id="camel_email_context">
>>    <routeBuilderRef ref="mailRoute" />
>>    <routeBuilderRef ref="emailMessageRoute" />
>>  </camelContext>
>>
>> <bean id="mailRoute" class="..." />
>> <bean id='mailConfigure' class="..." />
>>
>> <camelContext xmlns="http://activemq.apache.org/camel/schema/spring"
>> id="memoCreationContext">
>>        <routeBuilderRef ref="memoCreationRoute" />
>>  </camelContext>
>>
>> <bean id="memoCreationRoute" class="..." />
>>
>> I use jconsole to view the consumer/endpoints. The 2 contexts are created
>> OK. But their endpoints/consumers are all messed up:
>>
>> http://www.nabble.com/file/p21022918/ScreenShot001.jpg
>>
>> As you can see in the screenshot: only one consumer is created. The
>> "memoCreationContext" is not.
>> Also the endpoints of that "memoCreationContext" doesn't contain anything
>> except the Spring event.
>>
>> Thanks guys
>> --
>> View this message in context:
>> http://www.nabble.com/Multiple-Running-Context-tp21022918s22882p21022918.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
> 
> 
> 
> -- 
> 
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
> 
> 

-- 
View this message in context: http://www.nabble.com/Multiple-Running-Context-tp21022918s22882p21035441.html
Sent from the Camel - Users mailing list archive at Nabble.com.