[
https://issues.apache.org/jira/browse/QPID-8731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066779#comment-18066779
]
ASF GitHub Bot commented on QPID-8731:
--------------------------------------
gemmellr commented on PR #391:
URL: https://github.com/apache/qpid-broker-j/pull/391#issuecomment-4089733910
Moving to require 21 is increasingly reasonable, if possibly still a smidge
early (and probably not suited to a 10.0.2 like the Jira indicates), but just
in case it wasnt known/considered...there is a fairly simple way to retain Java
17 support and still enable the updated Subject usage required for Java 24+
with just a few-lines in a shim class(es) and a multi-release-jar built on the
newest JDK needed.
E.g. see
[here](https://github.com/apache/artemis/commit/8ec10217acb2403194be7c6bb7377d61624ffe50#diff-69b587111214bc26110691e2d9c2e78249aa3ba2444cae805922713d837ba12d)
for the changes used on Artemis when adding Java 25 support, specifically the
shim classes
[here
(24+)](https://github.com/apache/artemis/blob/2.52.0/artemis-commons/src/main/java24/org/apache/activemq/artemis/utils/sm/SecurityManagerShim.java)
and [here
(17-23)](https://github.com/apache/artemis/blob/2.52.0/artemis-commons/src/main/java/org/apache/activemq/artemis/utils/sm/SecurityManagerShim.java).
Noting thats likely far more complicated than what should be needed here as it
is actually retaining existing SecurityManager support on JDKs 17-23. Here its
possible just the callAs shim method would be needed.
> [Broker-J] Update broker build to java 21 / Security Manager removal
> --------------------------------------------------------------------
>
> Key: QPID-8731
> URL: https://issues.apache.org/jira/browse/QPID-8731
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Affects Versions: qpid-java-broker-10.0.1
> Reporter: Daniil Kirilyuk
> Priority: Major
> Fix For: qpid-java-broker-10.0.2
>
>
> The Security Manager was deprecated in Java 17 with [JEP
> 411|https://openjdk.org/jeps/411], and fully removed in Java 24 with [JEP
> 486|https://openjdk.org/jeps/486]. Broker-J relies on security
> manager-related APIs in a number of places, mostly to track the current
> subject. Refactoring is needed to enable the broker to run in a Java 24+
> environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
