Hi Justin, Thanks for the quick reply. We've only reproduced this inside of our ActiveMQ brokers running within Kubernetes in our development cluster. I haven't yet tried a local setup with the same configuration to be honest.
Here's a screenshot of the queues: https://drive.google.com/file/d/1WSE5-vwSgSTmucGhr0Xvpk040whrNNCT/view?usp=sharing I can send you the broker.xml with sensitive details redacted: https://drive.google.com/file/d/1veS5SYOM_uVTt_nSNQrmLX2smOQYVsVw/view?usp=sharing The protocol is OpenWire. Let me know if any more info can help. Also willing to try to reproduce locally if needed. Thank you! On Tue, Jun 11, 2024 at 6:10 PM Justin Bertram <jbert...@apache.org> wrote: > This behavior doesn't ring any bells. I've got a couple of questions: > > - Do you have a way to reproduce this? > - What protocol are your Java clients using? > - What routing type(s) are the queues using? > > > Justin > > On Tue, Jun 11, 2024 at 4:42 PM Vincent Simpson <vincef...@gmail.com> > wrote: > > > Hi, > > > > I am seeing in my console that my address: "fooQueue" has two queues > > attached to it, one with the same name as the address, and a duplicate > with > > a seemingly random number appended to the end such as "fooQueue-5", but > > I've never seen the number higher than 8 or 9. Messages are added to the > > queue seemingly randomly, and the console only shows the messages as > having > > been added, but not ever consumed, even though they are set to never > > expire. > > > > What would be the reason for this? I have the "auto-create-queues" > > attribute set to "true" in the broker.xml -- not sure if that is related. > > Also the consumers and producers of the queues are Java clients if that > > helps. > > > > Thanks much for any inputs! > > >
