Re: Persistence on a non transactional storage

[Tim Bain <tb...@alumni.duke.edu>]

Boris,

I'm not sure what the consequences would be if your underlying data store
doesn't support transactions and you simply perform a non-transactional
batch operation. I'd expect that recovery from failures wouldn't work
right, leaving some data written to the store when the broker expects it to
not be there, but I'd expect the non-error case to work OK. But this isn't
code I know well, unfortunately, so you may have to go through the source
code yourself (or you may have already done that).

Tim

On Thu, Aug 20, 2020, 1:41 AM Boris Granveaud <bo...@granveaud.com> wrote:

> Hello,
>
> I have a non transactional DB and would like to use it to persist ActiveMQ
> 5 messages. Does it seem possible?
>
> Javadoc of PersistenceAdapter says:
>
> "void beginTransaction(ConnectionContext context)
> This method starts a transaction on the persistent storage - which is
> nothing to do with JMS or XA transactions - its purely a mechanism to
> perform multiple writes to a persistent store in 1 transaction as a
> performance optimization."
>
> does it mean that I don't need DB transactions as long as I can guarantee
> that writes are performed together atomatically?
>
> thanks for your help,
> Boris.
>