Concurrency starts with the consumer. So thats your CXF RS endpoint. And that uses a http server under the hood (usually Jetty). And with that comes a thread pool for worker threads. So in your case 5 incoming requests is processed concurrently. Just like a HTTP server would do etc.
On Wed, Aug 22, 2012 at 7:59 PM, javakurious <javakuri...@gmail.com> wrote: > I am trying to deploy a REST webservice using cxf-camel . Following is the > overview of the route : > > <route id="A"> > <from uri="cxfrs:bean:rest-server"/> > <process ref="validate-params-processor"/> > <to uri="xslt:xslts/request-transformer.xsl"/> > <to uri="direct:requestProcessingQueue"/> > <to uri="xslt:xslts/response-transormer.xsl"/> > </route> > > <route id="B"> > <from uri="direct:requestProcessingQueue"/> > <process ref="request-processor"/> > </route> > > It is a SYNCHRONOUS webservice with request/reply. I am deploying it as a > .war in Glassfish 3.1 > > So, if 5 users are trying to access the webservice at the same time, will it > be sequential execution of the route ? OR are there going to be 5 instances > of the routeA and routeB(multiple beans, multiple xslt proecessors) ? > > Given the two requests can be handled completely independently and the route > is stateless, I would prefer a pool of routes instance. So, 5 concurrent > requests can be served 'simultaneously'. > > Can anybody point me in the right direction ? > > Thanks a lot > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/concurrent-users-with-camel-routes-tp5717888.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
