I came up with this feature. It is an oversight. The feature I did not need to have work with session recovery, just with transactions.
But even with transaction rollback, local tx rollback just causes session recovery anyway, so the same applies.
The only time the messages would get nacked back to the queue would be if the orginal local consumer that originally got the message had closed, otherwise it is just recovered directly to the local consumers.
* "If a transaction rollback is done, its produced messages are destroyed and its consumed
* messages are automatically recovered. For more information on session recovery, see Section
* 4.4.11 'Message Acknowledgment.'"