Broker-J is maintained, although not many people are currently working on it. Regarding the Java 17 compatibility, the issues you pointed out were fixed with QPID-8586 <https://issues.apache.org/jira/browse/QPID-8586> and QPID-8587 <https://issues.apache.org/jira/browse/QPID-8587>. Currently the main Broker-J branch should be able to be build both under Java 11 and Java 17.
Kind regards, Daniil Kirilyuk On Mon, 10 Oct 2022 at 17:35, Paul <pgallen...@randomlogic.com> wrote: > How about Broker-j, is it still being maintained? I posted in the dev > mailing list regarding a unit test issues last week and have received no > response. I am currently working on updating it (8.0.6 is the code base > I am working with) to Java 17 and building a native image (which > partially worked with Java 11). > > Thanks, > > PGA > > On 10/10/2022 2:32 AM, Gordon Sim wrote: > > ActiveMQ Artemis is probably the most obvious choice as it has the > > most ongoing activity. > > > > The fact is, as you point out, the c++ broker is not being actively > > maintained. Unless there are people willing to put in some time to do > > that, I think it is better to be clear about how things stand. > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >