Probably, there are many different protocols that can be used and the behaviors are all slightly different, mainly because the protocols are different. I think one workaround if you are using a protocol that automatically creates a queue when an address is created AND you desire a queue of a specific name is to create the address with a fully qualified queue name eg addressName::queueName, but if you want an address with no queues you have to create the address in the xml configuration
________________________________ From: Vincent Simpson <vincef...@gmail.com> Sent: Wednesday, June 12, 2024 12:10:04 PM To: users@activemq.apache.org <users@activemq.apache.org> Subject: Re: Multiple auto-created queues in Artemis So you’re thinking this may be an issue with our client code? We were also thinking it may be some sort of race condition because we have multiple replicas of a Java app that calls createQueue on the session On Wed, Jun 12, 2024 at 9:40 AM Jamy Spencer <jamy_spen...@hotmail.com> wrote: > I have seen this behavior with jms clients I think > > ________________________________ > From: Justin Bertram <jbert...@apache.org> > Sent: Tuesday, June 11, 2024 5:10:04 PM > To: users@activemq.apache.org <users@activemq.apache.org> > Subject: Re: Multiple auto-created queues in Artemis > > 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! > > >
