[
https://issues.apache.org/jira/browse/ARTEMIS-5948?focusedWorklogId=1009105&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1009105
]
ASF GitHub Bot logged work on ARTEMIS-5948:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Mar/26 14:05
Start Date: 11/Mar/26 14:05
Worklog Time Spent: 10m
Work Description: cortlepp commented on PR #6289:
URL: https://github.com/apache/artemis/pull/6289#issuecomment-4039456084
Currently
[org.apache.activemq.artemis.tests.integration.karaf.ArtemisFeatureTest](https://github.com/cortlepp/activemq-artemis/blob/062e5a2d9371b2c8c4ac8b3aba5b9cc9320e4b31/tests/karaf-server-integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/karaf/ArtemisFeatureTest.java#L152)
is failing in JDK 17 and 21 (it passes in JDK 25) on line 152. I can't really
tell from the test what the underlying problem is, since the test works with a
timeout it might also just be flakiness. If someone knows more about this I
would appreciate any advice.
Issue Time Tracking
-------------------
Worklog Id: (was: 1009105)
Time Spent: 0.5h (was: 20m)
> Use jctools-core-jdk11 Unsafe-free varhandle replacements
> ---------------------------------------------------------
>
> Key: ARTEMIS-5948
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5948
> Project: Artemis
> Issue Type: Improvement
> Reporter: Christian Ortlepp
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Artemis currently uses some queues from jctools-core which rely on
> sun.misc.Unsafe internally. These methods are deprecated in JDK24+, issue a
> warning at runtime and will be removed in future versions of the JDK. Thus it
> makes sense to switch to an implementation which does not rely on those
> methods.
> In their latest
> [release|https://github.com/JCTools/JCTools/releases/tag/v4.0.6] JCTools have
> started to publish a new artifact, jctools-core-jdk11, which contains
> alternative Varhandle based implementations which do not use Unsafe. As far
> as I understand them they are designed to be a drop-in replacement to the
> existing Unsafe implementations.
> It would be great if we could either switch to the new implementations
> entirely or provide it as an option somehow for the people that would like to
> avoid Unsafe. I will link a PR shortly where I switched over to the new
> implementation, but I am open to feedback if for example we can only do this
> change opt-in.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
