I'm not sure what you mean when you say, "I have also checked the same from Wildlfy side and it's looking fine." What exactly looks "fine" and what does "fine" mean?
At this point I don't see any reason to change the current behavior. Everything is working as designed. To restate what was said on Stack Overflow, the core messageID header is meant for internal use and is only displayed for informational or debugging purposes. Justin On Mon, Jan 4, 2021 at 7:37 AM Ranabir Chakraborty <[email protected]> wrote: > Hello, > > We have an issue in Wildlfy[1] where messageID cannot be used in a filter > via CLI. The messageID header property holds a java.lang.Long value, > however, it is not possible to use filter operators on the messageID header > property. > For example, the following expression would not work besides messageID in > each message was greater than '0'. > > [image: sample.png] > > [*standalone@localhost:9990 /] > /subsystem=messaging-activemq/server=default/jms-queue=A:count-messages(filter="messageID>0")* > > Today I saw something in Stackoverflow[2] where an engineer explains that > " Filters work on message properties and some selected attributes (e.g. > AMQDurable, AMQPriority, etc.). See the documentation for more details on > this. The message ID you're inspecting is not filterable. It's really > meant for internal use and only displayed for informational or debugging > purposes here." > > And I have also checked the same from Wildlfy side and it's looking fine. > I think it will require some changes in the Artemis /AMQ side. Can you > please take a look at this one? > > [1] https://issues.redhat.com/browse/WFLY-14241 > [2] > https://stackoverflow.com/questions/65490584/how-to-browse-message-by-id > > Thanks, > *Ranabir Chakraborty* > > Associate Software Engineer (JBoss SET) | Middleware Team > > Mob: +91-9733833958 > > <https://red.ht/sig> TRIED. TESTED. TRUSTED. > <https://redhat.com/trusted> >
