Hi Martin, Thanks for the report and the reproducer.
Yes, this is caused by the Security Manager being permanently disabled in JDK 24 (JEP 486). Broker-J currently relies on the Security Manager model in a number of places, so supporting JDK 24+ will require significant refactoring. Our current expectation is to deliver this in the next major Broker-J release (11.0.0). We don’t have a firm ETA yet, but it’s unlikely before summer/autumn this year. Kind regards, Daniil Kirilyuk On Thu, 8 Jan 2026 at 20:38, Martin Tržický <[email protected]> wrote: > Hi all, > > I've tried to migrate from Java 21 to 25, but I'm getting an error message: > Caused by: java.lang.UnsupportedOperationException: getSubject is not > supported > at java.base/javax.security.auth.Subject.getSubject(Subject.java:277) > at > > org.apache.qpid.server.logging.AbstractMessageLogger.getLogActor(AbstractMessageLogger.java:105) > at > > org.apache.qpid.server.logging.AbstractMessageLogger.getActor(AbstractMessageLogger.java:100) > at > > org.apache.qpid.server.logging.AbstractMessageLogger.message(AbstractMessageLogger.java:80) > at > > org.apache.qpid.server.SystemLauncher.lambda$startup$0(SystemLauncher.java:208) > at > > java.base/jdk.internal.vm.ScopedValueContainer.callWithoutScope(ScopedValueContainer.java:162) > at > > java.base/jdk.internal.vm.ScopedValueContainer.call(ScopedValueContainer.java:147) > at java.base/java.lang.ScopedValue$Carrier.call(ScopedValue.java:419) > at java.base/javax.security.auth.Subject.callAs(Subject.java:331) > at java.base/javax.security.auth.Subject.doAs(Subject.java:440) > at > org.apache.qpid.server.SystemLauncher.startup(SystemLauncher.java:198) > > Issue can be reproduced by running this example: > https://github.com/trzimar/issues/tree/master/qpid > > It is related to Security Manager being permanently disabled since JDK 24. > > Are there any plans to tackle this please? > > Regards, > Martin >
