You can use Jetty transport as workaround by setting the CXF endpoint address like this “http://YOUR_HOST_IP:ANOTHER_PORT/service/address"
-- 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 9:49:16 PM, snormanll ([email protected]) wrote: > Are you saying that the container is the issue, and that if we deploy to a > container that supports servlet spec v3.0 the issue will go away? > > If so, are there any strategies you can suggest for resolving the issue in > older containers? > > Thanks. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-CXF-Endpoint-Performance-Threading-tp5748984p5749101.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
