48 PM
To: users@activemq.apache.org
Subject: Re: auto-delete on addresses that still have a producer
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce
jointe à
Good to know, Robbie. Thanks for the clarification!
Justin
On Fri, Nov 3, 2023 at 12:45 PM Robbie Gemmell
wrote:
> nitpick: AMQP 1.0 also supports 'named producers'. Thats actually all
> the protocol supported until an additional capability was documented
> for doing 'anonymous producer' stuff
nitpick: AMQP 1.0 also supports 'named producers'. Thats actually all
the protocol supported until an additional capability was documented
for doing 'anonymous producer' stuff as e.g needed by some of JMS 1.1.
Though its worth noting all producers on the 'simplified api' added in
JMS 2.0 are effect
The broker does its best to track producers, but most protocols don't even
have the concept of a "named" producer (i.e. a producer that's registered
on the server to a particular endpoint). Most protocols only support
"anonymous" producers which can send to any endpoint at any time which
means in m
Classification: Public
Hello,
Today I noticed that an address was auto-removed while it still had a producer
active.
The producer has a very low production rate, its interval was above the value
of auto-delete-addresses-delay, so the timing constraints were still ok.
Nothing was broken and I ca
