Hi Daniil, I understand, thanks. I'll be watching the ticket for progress.
Regards, Martin út 27. 1. 2026 v 18:57 odesílatel Daniil Kirilyuk <[email protected]> napsal: > Hi Martin, > > We're working on making the broker compatible with Java 25, but the timing > is still uncertain. > > Kind regards, > > Daniil > > On Tue, 27 Jan 2026 at 17:02, Martin Tržický <[email protected]> > wrote: > > > Hi, > > I've noticed that this ticket was created: > > https://issues.apache.org/jira/browse/QPID-8731 > > So is there any chance that it will be fixed in the 10.0.2 version? > > Regards, > > Martin > > > > pá 9. 1. 2026 v 14:10 odesílatel Martin Tržický < > [email protected]> > > napsal: > > > > > Hi Daniil, > > > > > > Thanks for your quick response! It looks like I'll have to wait for a > > > while. > > > > > > Cheers, > > > Martin > > > > > > čt 8. 1. 2026 v 20:55 odesílatel Daniil Kirilyuk < > > > [email protected]> napsal: > > > > > >> 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 > > >> > > > >> > > > > > >
