I am currently using Jetty version 9.4.53.v20231009 alongside Apache Ignite 2.16 without any major issues. However, since community support for Jetty 9.4.53.v20231009 is coming to an end, I am working on upgrading to Jetty 12.0.13 to ensure continued security and feature support.
During this upgrade process, I encountered several significant changes between Jetty 9.x and Jetty 12.x, specifically in the Handler and javax namespaces. After making the necessary adjustments to align with Jetty 12.0.13’s new architecture, I ran into the following error:
java.lang.InstantiationException: org.eclipse.jetty.util.Pool
It seems the Pool class, which was previously a concrete class in Jetty 9.x, has now become an interface in Jetty 12.x. Despite updating my custom Jetty configuration, this error persists.
Could you please confirm whether Apache Ignite 2.16 officially supports Jetty 12.0.13? If not, are there any workarounds or plans to support this version in future Ignite releases?
Additional Context:
Current working setup: Jetty 9.4.53.v20231009 with Ignite 2.16
Upgrade target: Jetty 12.0.13 with Ignite 2.16
Encountered issue: java.lang.InstantiationException due to changes in org.eclipse.jetty.util.Pool
JDK version: Java 17
I am currently using Jetty version 9.4.53.v20231009 alongside Apache Ignite 2.16 without any major issues. However, since community support for Jetty 9.4.53.v20231009 is coming to an end, I am working on upgrading to Jetty 12.0.13 to ensure continued security and feature support.
During this upgrade process, I encountered several significant changes between Jetty 9.x and Jetty 12.x, specifically in the Handler and javax namespaces. After making the necessary adjustments to align with Jetty 12.0.13’s new architecture, I ran into the following error: java.lang.InstantiationException: org.eclipse.jetty.util.Pool
It seems the Pool class, which was previously a concrete class in Jetty 9.x, has now become an interface in Jetty 12.x. Despite updating my custom Jetty configuration, this error persists.
Could you please confirm whether Apache Ignite 2.16 officially supports Jetty 12.0.13? If not, are there any workarounds or plans to support this version in future Ignite releases?
Additional Context: Current working setup: Jetty 9.4.53.v20231009 with Ignite 2.16 Upgrade target: Jetty 12.0.13 with Ignite 2.16 Encountered issue: java.lang.InstantiationException due to changes in org.eclipse.jetty.util.Pool JDK version: Java 17
Environment: