Hi
Thanks for spotting & reporting this, I opened a JIRA to track this:
https://issues.apache.org/jira/browse/CAMEL-5485
In the future you're welcome to contribute to Apache Camel if you like:
http://camel.apache.org/contributing.html
Babak
--
View this message in context:
http://camel.465
Thank you, that did it: added cglib and operation name for the bean route.
Although for the moment it works, I don't necessarily like adding the
method name in the route, as I would have preferred to have the proxy more
generic - for all methods exposed by the webservice in the backend.
I ran the
Well apparently something is alleviated, but I'm trying to understand
what... The 2 queues are sequential, and the 1st queue is almost always
empty, so I cannot see why I have a bigger buffer.
On Sat, Aug 4, 2012 at 1:17 PM, Sam (Stephen Samuel)
wrote:
> With the intermediate queue you have a bi
Hi Brian,
find my answers inline...
Best,
Christian
On Sat, Aug 4, 2012 at 8:28 AM, Fitzcaraldo
wrote:
> Hi
>
> I'm exploring strategies for packaging routes for deployment in as .war.
> We
> have a parent POM with multiple child projects each representing a single
> route and each with its ow
With the intermediate queue you have a bigger buffer, a 2nd queue.
There might be a bottleneck on certain calls from your initial
endpoint which having the 2nd queue alleviates.
On Sat, Aug 4, 2012 at 9:48 AM, Xenofon Papadopoulos
wrote:
> Thanks for the tips. I'm trying, however, to understand w
Thanks for the tips. I'm trying, however, to understand why there is better
behavior with the intermediate queue, given that all other parameters
(threads etc) remain the same.
Also this is a test; in production we normally use about 800 concurrent
consumers, and the resource use in the servers is
Really nice!
Babak
bibryam wrote
>
> Hi all,
>
> Based on camel-twitter example I created a simple Camel application that
> displays twitter images about London 2012 Olympics.
> You can see the app running here [1] or read my post about it [2] :)
>
> [1] tinyurl.com/camelympics
> [2]
> http: