We observe the following: CXF 3.1.4 in Karaf 4.0.4, with pax web, and thus jetty 9.2.something.
When we have hundreds of outstanding async requests, a thread from Jetty starts eating CPU time; it uses up an entire core -- it's spending time in some method of some Eclipse blocking queue class. 1: Has anyone else seen anything like this? 2: We sort of suspect that things might be happier in Jetty 9.3; does anyone have experience in Karaf of ignoring pax-web and just letting the CXF http transport grab a port and get busy? I can supply more details, and I think that I'm doomed to build an 'available on github' test case eventually.
