This feature supports the publishers and non-durable subscriber with non-temp topic only. The reconnect logic will throw exception if a client attempts to create either a queue receiver (for temp or non-temp queue) or a durable subscriber or non-durable subscriber with a temp topic in a multiple Broker Server deployment.

If this feature is enabled for non-durable subscribers with a non-temp topic, a reconnection might result in data loss.

A client can only create a durable subscription in a non-clustered or single Broker Server deployment.