Edson is right, and you can follow his pointers for additional details. In short, there's a bug. The queue with the problem browsing messages has a message with a null property value and that is triggering an exception on the broker so that the messages cannot be browsed. A null property value is perfectly valid, so you're not doing anything wrong.
Justin On Wed, Mar 2, 2022 at 2:45 AM Toni Perez <[email protected]> wrote: > We have an Artemis 2.20.0 with one queue (MULTICAST) attached to an > address configured with > > > <auto-create-dead-letter-resources>true</auto-create-dead-letter-resources> > > <management-message-attribute-size-limit>-1</management-message-attribute-size-limit> > > <!-- default is 0 (no delay) 600000 = 10 minutes--> > <redelivery-delay>600000</redelivery-delay> > <max-delivery-attempts>1000</max-delivery-attempts> > <dead-letter-address>DLQ</dead-letter-address> > <expiry-address>ExpiryQueue</expiry-address> > <!-- with -1 only the global-max-size is in use for limiting > --> > <max-size-bytes>-1</max-size-bytes> > > <message-counter-history-day-limit>10</message-counter-history-day-limit> > <address-full-policy>PAGE</address-full-policy> > <auto-create-queues>true</auto-create-queues> > <auto-create-addresses>true</auto-create-addresses> > <auto-create-jms-queues>true</auto-create-jms-queues> > <auto-create-jms-topics>true</auto-create-jms-topics> > <auto-delete-queues>false</auto-delete-queues> > <auto-delete-addresses>false</auto-delete-addresses> > > > If we try to browse the queue and try to view the messages, the web > console say "No Items Available" but the message count is 6. On the other > hand if we try to browse the DLQ queue we can view the messages. > > > Are we doing something wrong? > > > Best regards, > -- > Toni Pérez Fernández > IT Department > > > Grupo Festina Lotus, S.A. > Vía layetana 20, 4ª - 08003 Barcelona >
