Hi Martin-
Even non-persistent message flows often take advantage of the message storage.
When the broker runs out of memory for non-persistent messages, it will swap
them to disk using the temp store. That is generally preferred over back
pressure, producer flow control or stalling out message flow.
Also— for non-persistent HA with two or more brokers, you can use priority
url’s to maintain ordering, instead of using a lease locker.
Thanks,
Matt Pavlovich
> On Nov 29, 2023, at 2:19 AM, Martin Lichtin <lich...@yahoo.com.INVALID> wrote:
>
> I'd like to configure ActiveMQ classic for non-persistent messaging, with a
> database lease locker.
> How can this be done?
>
> Configuring <broker persistent="false" ... > then at startup it says:
>
> persistent="false", ignoring configured persistenceAdapter
>
> but the "lease-database-locker" must be configured inside:
>
> <persistenceAdapter>
> <mKahaDB lockKeepAlivePeriod="1000">
> <locker>
> <lease-database-locker leaseHolderId="${broker-id:root}" >
> <statements>
> <statements lockTableName="activemq_lock" />
> </statements>
> </lease-database-locker>
> </locker>
> </mKahaDB>
> </persistenceAdapter>
