I don't see anything problematic. Work up some kind of reproducible test
and I'll try to carve out some time to take a look.
Justin
On Thu, Feb 24, 2022 at 2:23 PM Edson Richter <edsonrich...@hotmail.com>
wrote:
> Ok, I would need some help identifying Where is my fault. Please advise.
> I don’t see anything null in here:
>
>
> 2022-02-24 17:15:34,530 DEBUG
> [org.apache.activemq.artemis.core.protocol.stomp.StompConnection] STOMP(/
> 192.168.0.30:60724, f7986f29): IN << StompFrame[command=CONNECT,
> headers={accept-version=1.0,1.1,1.2, heart-beat=60000,60000,
> host=192.168.0.250, login=******, passcode=****}]
> 2022-02-24 17:15:34,532 DEBUG
> [org.apache.activemq.artemis.core.protocol.stomp.StompConnection] STOMP(/
> 192.168.0.30:60724, f7986f29):OUT >> StompFrame[command=CONNECTED,
> headers={version=1.2, session=f7986f29, server=ActiveMQ-Artemis/2.20.0
> ActiveMQ Artemis Messaging Engine, heart-beat=60000,60000}]
> 2022-02-24 17:15:34,535 DEBUG
> [org.apache.activemq.artemis.core.protocol.stomp.StompConnection] STOMP(/
> 192.168.0.30:60724, f7986f29): IN << StompFrame[command=SEND,
> headers={destination=dtrecvrech000049dev::dtrecvrech000049dev,
> content-type=application/json, persistent=true},
> body={"status":-5,"message":"O sistema Rech retornou um código de resposta
> 401. A chave do CT-e é .\nA mensagem do sistema é
> {\"status\":{\"code\":-1,\"message\":\"Não autorizado\"}}","ctcChave":""},
> body-bytes=[123, 34, 115, 116, 97, 116, 117, 115, 34, 58, 45, 53, 44, 34,
> 109, 101, 115, 115, 97, 103, 101, 34, 58, 34, 79, 32, 115, 105, 115, 116,
> 101, 109, 97, 32, 82, 101, 99, 104, 32, 114, 101, 116, 111, 114, 110, 111,
> 117, 32, 117, 109, 32, 99, -61, -77, 100, 105, 103, 111, 32, 100, 101, 32,
> 114, 101, 115, 112, 111, 115, 116, 97, 32, 52, 48, 49, 46, 32, 65, 32, 99,
> 104, 97, 118, 101, 32, 100, 111, 32, 67, 84, 45, 101, 32, -61, -87, 32, 46,
> 92, 110, 65, 32, 109, 101, 110, 115, 97, 103, 101, 109, 32, 100, 111, 32,
> 115, 105, 115, 116, 101, 109, 97, 32, -61, -87, 32, 123, 92, 34, 115, 116,
> 97, 116, 117, 115, 92, 34, 58, 123, 92, 34, 99, 111, 100, 101, 92, 34, 58,
> 45, 49, 44, 92, 34, 109, 101, 115, 115, 97, 103, 101, 92, 34, 58, 92, 34,
> 78, -61, -93, 111, 32, 97, 117, 116, 111, 114, 105, 122, 97, 100, 111, 92,
> 34, 125, 125, 34, 44, 34, 99, 116, 99, 67, 104, 97, 118, 101, 34, 58, 34,
> 34, 125], size=0]
> 2022-02-24 17:15:34,537 DEBUG
> [org.apache.activemq.artemis.core.protocol.stomp.StompConnection] STOMP(/
> 192.168.0.30:60724, f7986f29): IN << StompFrame[command=DISCONNECT,
> headers={receipt=5}]
> 2022-02-24 17:15:34,537 DEBUG
> [org.apache.activemq.artemis.core.protocol.stomp.StompConnection] STOMP(/
> 192.168.0.30:60724, f7986f29):OUT >> StompFrame[command=RECEIPT,
> headers={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@activemq.apache.org<mailto:users@activemq.apache.org>
> Assunto: Re: ARTEMIS-3677 mitigate NPE when browsing messages
>
> > Is there a way to log what ActiveMQ is receiving from my STOMP client?
>
> See this documentation [1].
>
>
> Justin
>
> [1]
>
> https://activemq.apache.org/components/artemis/documentation/latest/stomp.html#logging
>
> On Thu, Feb 24, 2022 at 11:18 AM Edson Richter <edsonrich...@hotmail.com>
> wrote:
>
> > 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
> > >
> > >
> >
> >
>
>
