Bert

The order of events I see (see also attached logs) is: (1) we call server.stop() (2) first debug log of request is generated by jetty server (3) server is waiting...

In attachment you can find a simple unit test that shows the issue. [jetty-test.zip](https://github.com/eclipse/jetty.project/files/9083258/jetty-test.zip)

Uploaded slightly wrong file. Here's a better one: [jetty-unit-test.zip](https://github.com/eclipse/jetty.project/files/9093127/jetty-unit-test.zip)

FYI, from the code I can see that this is a 9.4.x issue only. In 10.x it is fixed.

Thanks for the advice. It is indeed already fixed in 10.x. We have upgraded to 10.x already, but our older branches which we still need to support run jetty 9...

The order of events I see is: (1) we call server.stop() (2) first debug log of request is generated by jetty server (3) server is waiting for other ongoing requests...