RE: ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException

2024-02-01 Thread Mika Raty (Nokia)
-Baptiste Onofré Sent: Tuesday, January 30, 2024 6:24 PM To: users@activemq.apache.org Subject: Re: ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException [Et saa yleensä sähköpostia j...@nanthrax.net. Lisätietoja siitä, miksi tämä on tärkeää, on

Re: ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException

2024-01-30 Thread Jean-Baptiste Onofré
Hi Mika, It's related to the RuntimeConfigurationPlugin and its JAXB usage. It needs an additional lib to work out of the box. I propose to create a Jira, providing the workaround you can use and fix in next 5.18.x release. Sorry for the inconvenience (I didn't test RuntimeConfigurationPlugin to

ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException

2024-01-30 Thread Mika Raty (Nokia)
Hello everyone, We are upgrading from java 8 to java 17 in a project that uses ActiveMQ 5.18.3 and we noticed that when we try to use the JMX operation updateNow that is available from Bean org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin using java