Re: ARTEMIS-3677 mitigate NPE when browsing messages

2022-02-24 Thread Justin Bertram
> > De: Justin Bertram > Enviado: Thursday, February 24, 2022 11:25:23 PM > Para: users@activemq.apache.org > Assunto: Re: ARTEMIS-3677 mitigate NPE when browsing messages > > The stack-trace indicates that the NPE is, in fact, being triggere

Re: ARTEMIS-3677 mitigate NPE when browsing messages

2022-02-24 Thread Justin Bertram
hannelEndPoint.java:104) > at > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) > at > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) > at > org.eclipse.jetty.util.thread.strategy.Ea

Re: ARTEMIS-3677 mitigate NPE when browsing messages

2022-02-24 Thread Justin Bertram
tion.java:277) > at org.eclipse.jetty.io > .AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) > at org.eclipse.jetty.io > .FillInterest.fillable(FillInterest.java:105) > at org.eclipse.jetty.io > .ChannelEndPoint$1.run(ChannelEndPoint.java:104) > at > org.eclip

Re: ARTEMIS-3677 mitigate NPE when browsing messages

2022-02-24 Thread Justin Bertram
ders={receipt-id=5}] > > > Thanks once again 😊 > > ER > > > Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para > Windows > > De: Justin Bertram<mailto:jbert...@apache.org> > Enviado:quinta-feira, 24 de fevereiro de 2022 14:22 > Para: users@ac

Re: ARTEMIS-3677 mitigate NPE when browsing messages

2022-02-24 Thread Justin Bertram
ows > > 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 ActiveM

Re: ARTEMIS-3677 mitigate NPE when browsing messages

2022-02-23 Thread Justin Bertram
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 va