Ok, that was a swift answer... However I'm not sure I follow your suggestion. Basically the only thing I want to do is to ramp up the number of executing threads in Jetty. Not sure what the default settings are but it doesn't seem to scale much beyond 5 concurrent threads from my load test in soap ui.
Is there a better way to configure this on a global level or do I actually have to do it per deployed end point? If I have to do it per endpoint then I'm not sure I follow your suggestion to /"Consider binding the DOSGI endpoints to HttpService which may help with picking up container-specific HTTP configs"/ Do you mean to create BundleActivator and somehow deploy my endpoint to the HTTPService? I have not found any examples/documentation on how this would be done. So far I've spent a considerable amount of hours to figure out how to perform a configuration that should be a basic task so I'm a bit confused why it must be so complicated. -- View this message in context: http://cxf.547215.n5.nabble.com/Fail-to-deploy-webservice-with-httpj-engine-factory-config-tp5088923p5088979.html Sent from the cxf-user mailing list archive at Nabble.com.
