Hi Fred- Most likely, you are seeing a _redelivery_ vs a bug or actual duplicate message.
First thing to confirm that it is in fact the same message by comparing messageId, and not just properties or message body content. There are scenarios where a producer may inadvertently send the same message a second time, which is a double-send (and not a duplicate). This type of environment-specific issue is generally beyond what is feasible to support over an email mailing list of volunteers. A couple things to go check out to see if there are any errors or unexpected log messages indicating some sort of network or other system issue that may lead to what you are seeing. 1. Database server logs 2. ActiveMQ broker logs 3. Application consumer logs Hope this helps get you pointed down the path to solve for it. Thanks, Matt > On Mar 1, 2024, at 9:52 AM, Frédéric Curvat <fcur...@gmail.com> wrote: > > Hello ! > > At my company we are using Apache ActiveMQ 5.18.3. > We suspect that in some rare cases, a queue message is read twice by > different consumers. > For more context : > - broker is classic primary/secondary (secondary started but not active - > not a network of brokers). > - we are using persisted queues with PostgreSQL backend. > - A single queue is being read by several consumers : 10 consumers for a > single java app deployed in HA other several k8s pods. > - We use SESSION_TRANSACTED session for either consumers and producers. > - We use PooledConnectionFactory with 1 connection, > maximumActiveSessionPerConnection 500, expiryTimeout 10000 > We see no transaction or other error in logs, either service of activemq > broker at the time of the "double read". > > Has something like this already been seen ? Can it be a bug or a > misconfiguration somewhere ? > > Best, > > Fred
