"Guaranteed Message Publish Window Size" with (Solace) JMS

Hi @marc,
sorry to bring up that old topic again, but we just ran into this issue and I’ve found your notes here.
What confuses me a lot is the part of the documentation that says: “for non-persistent guaranteed messages sent by the Publisher”.

So, how could a non-persistent message be guaranteed?

Or in other words, our szenario is like that:
We’re sending JMS messages to a dynamic Solace Topic (including country code and other dynamic values) on an HA Broker and have - depending on the dynamic values - around 1 to 50 queues with matching subscriptions per message.

As we cannot tollerate any data loss, we assumed persistent is the right and obvious setting, however - what would be the difference in this scenario if we’d choose Non-Persistent?
Would the message be ACKed to the Publisher before it is persisted in any of the subscribing queues or synched to the passive node?

best regards
Andreas