Hi It looks like you deploy the camel route into websphere. CXF support the servlet continuation if the servlet container supports Servlet 3.0. In that way CXF consumer uses the async invocation which doesn't block the worker thread any more.
-- 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 March 19, 2014 at 8:07:56 PM, snormanll ([email protected]) wrote: > Here's a sample stack trace for a slow transaction: > > / > com.ibm.ws.util.ThreadPool$Worker:run:1646 (method time = 0 ms, total time = > 28492 ms) > org.apache.cxf.transport.servlet.AbstractHTTPServlet:service:262 (method > time = 0 ms, total time = 28492 ms) > HTTPServlet:service:738 (method time = 0 ms, total time = 28492 ms) > org.apache.cxf.transport.servlet.AbstractHTTPServlet:doPost:206 (method > time = 0 ms, total time = 28492 ms) > org.apache.cxf.transport.servlet.AbstractHTTPServlet:handleRequest:286 > (method time = 0 ms, total time = 28492 ms) > org.apache.cxf.transport.servlet.CXFNonSpringServlet:invoke:167 (method > time = 0 ms, total time = 28492 ms) > org.apache.cxf.transport.servlet.ServletController:invoke:153 (method > time = 0 ms, total time = 28492 ms) > org.apache.cxf.transport.servlet.ServletController:invoke:222 (method > time = 0 ms, total time = 28492 ms) > > org.apache.cxf.transport.servlet.ServletController:invokeDestination:248 > (method time = 0 ms, total time = 28492 ms) > org.apache.cxf.transport.http.AbstractHTTPDestination:invoke:239 > (method time = 0 ms, total time = 28492 ms) > org.apache.cxf.transport.ChainInitiationObserver:onMessage:121 > (method time = 0 ms, total time = 28492 ms) > org.apache.cxf.phase.PhaseInterceptorChain:doIntercept:272 > (method time = 0 ms, total time = 28492 ms) > Web Service - > org.apache.cxf.interceptor.ServiceInvokerInterceptor:handleMessage:107 > (method time = 0 ms, total time = 28492 ms) > org.apache.cxf.workqueue.SynchronousExecutor:execute:37 (method > time = 0 ms, total time = 28492 ms) > Proxy For Web Service - > org.apache.cxf.interceptor.ServiceInvokerInterceptor:run:58 (method time = > 0 > ms, total time = 28492 ms) > org.apache.camel.component.cxf.CxfConsumer$1:invoke:75 > (method time = 0 ms, total time = 28492 ms) > org.apache.camel.component.cxf.CxfConsumer$1:syncInvoke:134 > (method time = 0 ms, total time = 28492 ms) > > org.apache.camel.processor.DelegateAsyncProcessor:process:87 (method time > = > 0 ms, total time = 28492 ms) > org.apache.camel.util.AsyncProcessorHelper:process:121 > (method time = 28492 ms, total time = 28492 ms) > / > > The CXF proxy client classes we're using are generated from a WSDL using the > maven "cxf-codegen-plugin" plugin. That would be the CXF bean being exposed > as the service interface in the Camel route: > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-CXF-Endpoint-Performance-Threading-tp5748984p5749099.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
