CAMEL-5261.
Thomas
2012/5/9 Claus Ibsen
> On Tue, May 8, 2012 at 6:12 PM, Thomas Johansen wrote:
> > Hi again,
> >
> > The problem goes for both seda and vm. BUT I discovered that the problem
> > only arises when the vm/seda route is adviced with
> > interceptSendToEndpoint(). And still only o
On Tue, May 8, 2012 at 6:12 PM, Thomas Johansen wrote:
> Hi again,
>
> The problem goes for both seda and vm. BUT I discovered that the problem
> only arises when the vm/seda route is adviced with
> interceptSendToEndpoint(). And still only on 2.9.1/2.9.2, not 2.9.0.
>
> I'm attaching my stripped
Hi again,
The problem goes for both seda and vm. BUT I discovered that the problem
only arises when the vm/seda route is adviced with
interceptSendToEndpoint(). And still only on 2.9.1/2.9.2, not 2.9.0.
I'm attaching my stripped down test. It is all green on Camel 2.9.0 and 2
out of 4 fail on Cam
On Tue, May 8, 2012 at 4:08 PM, Thomas Johansen 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
>
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.
Takk
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
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("v
