Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAET125bNo0b0b1gHvbp5srhQ995MtL0i9USrZNM9nzM9iPkpzw@mail.gmail.com>
References: 
 <CAET125YstU=u_seyE=fvxZVv0jDqwkr4-YSjdVFewR_ED5=7Rw@mail.gmail.com>
 <CAGB5yNkDbQicQ+kGdwx78X0M2hEfWOV-L7h--KF=m9oBseaAWg@mail.gmail.com>
 <CAET125bNo0b0b1gHvbp5srhQ995MtL0i9USrZNM9nzM9iPkpzw@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 8 May 2012 16:23:58 +0200
Message-ID: 
 <CAGB5yNm0OFkvTAsLBh5nj+6_M9E8MOAKqkgEbMzJ13N2achKFA@mail.gmail.com>
Subject: Re: VM component, URI for matching
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, May 8, 2012 at 4:08 PM, Thomas Johansen <thxmasj@gmail.com> wrote:
> Hi Claus,
>
> So what's the deal? This is certainly an incompatibility between 2.9.0 and
> 2.9.1/2.9.2? On 2.9.1/2.9.2 the producer and consumer don't communicate
> when having the option on the consumer and not on the producer. This makes
> upgrading Camel in my product from 2.9.0 to 2.9.2 difficult.
>

You are the first to report this, and there has been 2 patch releases
2.9.1 and 2.9.2.
So maybe you do something odd / different than others.

And have you tested with SEDA.

And can you create a sample unit tests that demonstrates the issue?

And have you tried TRUNK source code.


> Takk,
> Thomas
>
> 2012/5/8 Claus Ibsen <claus.ibsen@gmail.com>
>
>> Hi
>>
>> Yeah only the name of the queue ought to be enough.
>> Its only on the consumer side the ?concurrentConsumers option matter.
>>
>> The only trick is though if you want the queue to have a fixed size,
>> then its frankly the first endpoint
>> created that dicate the queue size, eg if you use vm:foo?size=5000
>>
>>
>>
>> On Tue, May 8, 2012 at 2:57 PM, Thomas Johansen <thxmasj@gmail.com> wrote:
>> > Hi,
>> >
>> > Camel 2.9.0 apparently does not require that URI parameters are part of
>> the
>> > URI on both consumer and producer side of a VM queue, while 2.9.1 and
>> 2.9.2
>> > does. Is this by purpose or mistake?
>> >
>> > For example, I had a test which was using a ProducerTemplate to test a
>> > route:
>> >
>> > template().requestBody("vm:MyReceiver", request);
>> >
>> > and the route:
>> >
>> > from("vm:MyReceiver?concurrentConsumers=1")...
>> >
>> > This worked in 2.9.0 but not with 2.9.1 and 2.9.2 until i changed the
>> test
>> > to do:
>> >
>> > template().requestBody("vm:MyReceiver?concurrentConsumers=1", request);
>> >
>> >
>> > Takk,
>> > Thomas
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>


-- 
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/