Since the Java 25 release, I am seeing this in the logs:
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.hubspot.horizon.shaded.com.ning.http.client.providers.netty.chmv8.ConcurrentHashMapV8 (file:/Users/davidcockbill/.m2/repository/com/hubspot/HorizonNing/0.1.1/HorizonNing-0.1.1.jar)
WARNING: Please consider reporting this to the maintainers of class com.hubspot.horizon.shaded.com.ning.http.client.providers.netty.chmv8.ConcurrentHashMapV8
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release
The issue is with the way netty (an asynchronous event-driven network application framework) uses memory by bypassing the heap (and garbage collection). Since Java 24 the use of the unsafe methods produces the warning shown.
Netty have tried to fix, but had performance issues, so pulled the fix.
https://github.com/netty/netty/wiki/Java-24-and-sun.misc.Unsafe
So from Netty 4.2.2 onward (providing you are running in Java 25 onwards) they have replaced with using MemorySegments. However looks like we want to use 4.2.3 with the following JVM argument: --enable-native-access=io.netty.common
So we need the chromedevtools-client to upgrade netty to 4.2.3.
I believe HorizonNing 0.5.1 updated the netty version. I tried building with this new version, but got duplicate netty version errors.
Since the Java 25 release, I am seeing this in the logs:
The issue is with the way netty (an asynchronous event-driven network application framework) uses memory by bypassing the heap (and garbage collection). Since Java 24 the use of the unsafe methods produces the warning shown.
Netty have tried to fix, but had performance issues, so pulled the fix.
https://github.com/netty/netty/wiki/Java-24-and-sun.misc.Unsafe
So from Netty 4.2.2 onward (providing you are running in Java 25 onwards) they have replaced with using MemorySegments. However looks like we want to use 4.2.3 with the following JVM argument:
--enable-native-access=io.netty.commonSo we need the chromedevtools-client to upgrade netty to 4.2.3.
I believe HorizonNing 0.5.1 updated the netty version. I tried building with this new version, but got duplicate netty version errors.