-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
5.1.0.Beta11
-
None
-
False
-
-
False
-
Low
We use "org.wildfly.arquillian:wildfly-arquillian-container-managed" 5.1.0.Beta11 in https://github.com/arquillian/arquillian-extension-warp, and WildFly 37.0.1.Final in the test suite.
The profile "wildfly-managed" prints this warning when running the test suite with Java 24:
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called WARNING: sun.misc.Unsafe::objectFieldOffset has been called by org.jboss.threads.JBossExecutors (file:/C:/Users/USERNAME/.m2/repository/org/jboss/threads/jboss-threads/2.4.0.Final/jboss-threads-2.4.0.Final.jar) WARNING: Please consider reporting this to the maintainers of class org.jboss.threads.JBossExecutors WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release INFO 2025-09-07T10:28:02,066 [main] jboss.threads.<clinit> (Version.java:52) - JBoss Threads version 2.4.0.Final
Where does this rather outdated jboss-threads version come from (released in 2020)? Maven reports this dependency tree (full output attached):
[INFO] +- org.wildfly.arquillian:wildfly-arquillian-container-managed:jar:5.1.0.Beta11:test [INFO] | +- org.wildfly.arquillian:wildfly-arquillian-common:jar:5.1.0.Beta11:test ... [INFO] | | +- org.wildfly.core:wildfly-controller-client:jar:27.0.1.Final:test [INFO] | | | +- org.wildfly.core:wildfly-protocol:jar:27.0.1.Final:test [INFO] | | | | +- org.jboss.modules:jboss-modules:jar:2.1.6.Final:test [INFO] | | | | +- org.jboss.remoting:jboss-remoting:jar:5.0.30.Final:test [INFO] | | | | | \- org.wildfly.security:wildfly-elytron-sasl-auth-util:jar:2.5.0.Final:test ... [INFO] | | | +- org.jboss:jboss-dmr:jar:1.7.0.Final:test [INFO] | | | +- org.jboss.threads:jboss-threads:jar:2.4.0.Final:test
Maybe related to WFARQ-207 ?
- is blocked by
-
WFCORE-7040 Move to SE 17 as the minimum SE version
-
- Resolved
-
-
WFCORE-7045 Upgrade jboss-threads to 3.9.x
-
- Resolved
-
- is incorporated by
-
WFARQ-216 Upgrade to WildFly Core 29.0.1.Final
-
- Open
-