Hi, This JEP has the potential to have a significant impact with Tomcat's JNI use starting with Java 26. https://openjdk.org/jeps/471
Unsafe.invokeCleaner will be removed, which will effectively prevent using the direct ByteBuffers that are needed for tomcat-native. The solution is to use a memory segment from FFM, then call MemorySegment.asByteBuffer, which creates a direct ByteBuffer with a controllable lifecycle. So using JNI would require FFM and using the full FFM code instead should make more sense. We will of course have to see how things turn out ... Another, less problematic, yet still annoying change will be https://openjdk.org/jeps/472 in Java 24+. Basically, the native access flag use will become mandatory. This is a bit annoying since it is not possible to add "--enable-native-access=ALL-UNNAMED" in the default command line without breaking on older Java. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
