Just one point... I’m not sending any null atributes; except the cause is that I’m not sending a unique identifier. Is there a way to log what ActiveMQ is receiving from my STOMP client?
Thanks, ER Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows De: Justin Bertram<mailto:jbert...@apache.org> Enviado:quarta-feira, 23 de fevereiro de 2022 12:15 Para: users@activemq.apache.org<mailto:users@activemq.apache.org> Assunto: Re: ARTEMIS-3677 mitigate NPE when browsing messages The next release of ActiveMQ Artemis will be 2.21.0. There is no 2.20.1 release planned. I expect 2.21.0 to be tagged and sent for a vote before the end of this quarter (i.e. March 31). In the mean-time you have a couple ways to mitigate the issue: 1) Don't send messages with a null property value. 2) Build the current "main" branch using "mvn clean install -Prelease -DskipTests" and then replace your broker's existing lib/artemis-core-client-*.jar with the one put into artemis-distribution/target/apache-artemis-2.21.0-SNAPSHOT-bin/apache-artemis-2.21.0-SNAPSHOT/lib/. Justin On Wed, Feb 23, 2022 at 9:06 AM Edson Richter <edsonrich...@hotmail.com> wrote: > Hi! > > There is a plan to release a 2.20.1 version of Artemis? I’m plagued by > ARTEMIS-3677 mitigate NPE when browsing message which is already fixed in > source code. > If there is a roadmap on planned future releases, I would look there, to > not disturb the list 😊 > > Thanks, > > Edson Richter > > > Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para > Windows > >
