Hi, If your route cannot hold the request for enough time, your last request may not be blocked.
Please take a look at this question[1] in stack overflow. [1]http://stackoverflow.com/questions/20632706/apache-restlet-connector-overload -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On October 6, 2014 at 3:13:05 PM, Alexander Lvov ([email protected]) wrote: > Hello dear Camel developers! I am a developer who have been using Camel and > building routes > for over a year. Right now we are trying to see how we should configure out > restlet in terms of availability and perfomance and i recognised that the > restlet settings doesnt seem to work. Here is the config for restlet we are > experimented with: > > > > > class="org.apache.camel.component.restlet.RestletComponent"> > > > > > > > > > Producing over 11 requests within a minute in different threads using > TaskExecutor does not lead to any form of rejected or timeout service. Why > is that so? Please help! > > I realise its not the prettiest config to blend constructor and properties > but it should work! > I verified there is no overriding bean or similiar by checking bean > settings in the route like this: > > ((SpringCamelContext) context).getApplicationContext().getBean("restlet") > > We are using Camel 2.12 and spring 3.2.4. > > Sorry for typos > BR > Alex >
