Thanks for the answer.
Question: Why do you want to disable reconnect on Solace session ?
Because it opens additional opportunity for gaps: Situation when publisher publishes A and B but because of disconnection B is not delivered to the broker. But then publisher reconnects and successfully publishes C.
You know, that you can publish to a topic and still use guaranteed messaging ?
Actually I didn’t know it.
Does that answer your question ?
Additionally what can publisher do to prevent gaps which can’t be detected by a consumer? Eg. I’m ok if after losing B I lose all messages after it. But I would like to avoid situation that I’ll lose some message in the middle or messages are delivered in a different order.