Let me know if you find a way to reproduce this. I can't recall seeing this behavior before so I'm at a loss as to what might be causing it. I think I'll need a way to reproduce it to investigate further.
Keep in mind that invoking createQueue on a JMS Session object only creates a local instance of a Queue object. It doesn't create a queue on the broker itself. When the client actually uses the queue (e.g. by sending a message or creating a consumer) the broker will then create the queue (and address) automatically by default. If the queue exists already (e.g. because it was just created for another client) the broker should simply use the existing queue. It shouldn't create a new queue with an increasing index (e.g. "-0", "-1", etc.). Justin On Wed, Jun 12, 2024 at 1:18 PM Vincent Simpson <vincef...@gmail.com> wrote: > We use only the address to connect. Yeah so a weird thing we’re doing on > the client side is calling createQueue with the same value as the address, > BUT have also configured in the broker.xml to set auto-create-queues and > auto-create-addresses to true. Maybe there is some race condition with that > > On Wed, Jun 12, 2024 at 1:42 PM Jamy Spencer <jamy_spen...@hotmail.com> > wrote: > > > 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! > > > > > > > > > >
