Joakim Erdfelt

Do we want this in Jetty 10.0.10 release?

Skipping this release, moving to 10.0.12 / 11.0.12 release.

@lachlan-roberts you can merge this one now.

To repeat what @gregw pointed out ... Jetty 9.4.x is now at End of Community Support and is scheduled to be EOL in 6 months. * #7958

Trying to address this specifically in PR #8416

Is there a reason you are using an old logback? This is a known issue in Logback 1.2.x series. * See https://jira.qos.ch/browse/LOGBACK-1492 For Jetty 10 and Jetty 11 we use...

> Also reproduced on Jetty 10.0.10, but cannot reproduce on 10.0.9 The class named `AdaptiveExecutionStrategy` came into being for release 10.0.6. It had an update in release 10.0.8 for javadoc,...

Lets look at the history of this lock in `toString()`. As if this was a concern, it would happen for far more of a range then just 10.0.10 thru 10.0.9....

> @joakime Logback 1.2.* is not abandoned and in fact is being developing in parallel with 1.3.* Migration to the latest version is not an option right now due to...

> As a simple fix `this` reference can be replaced with explicit `toString()` call: > `LOG.debug("{} tryProduce {}", this, wasPending)` -> `LOG.debug("{} tryProduce {}", this.toString(), wasPending)` > If you find...