Re-submit from DLQ from HawtIO When using networkbridge, default TTL causes stuck messages.

Issue

• Have network of brokers setup, using a complete graph, dynamic only. Didn't set any TTL, so default to 1.
• This works great, but when retrying from a dead letter queue, using the 'Move' option in Hawt.io, the messages will be stuck if a consumer is not connect to that broker AND brokerPath has a brokerId.
• Is there any configuration that can be added, other than increasing the TTL? Concerned it could still happen if TTL > 1 as it could move around the network before ending up in the DLQ for some other reason.
• This is the networkbridge setup:

        <networkConnectors>
            <networkConnector uri="static:(<broker hosts>, ...)" userName="<user>" password="<pass>" dynamicOnly="true" />
        </networkConnectors>

This is the policy entry for dead letter queue:

                    <policyEntry queue="rdl.>" producerFlowControl="true" memoryLimit="1mb">
                        <deadLetterStrategy>
                            <!-- Use the prefix 'DLQ.' for the destination name, and make the DLQ a queue rather than a topic -->
                            <!-- Set endableAudit = false to prevent queues messages from disappearing when resubmitted from DLQ and failing again -->
                            <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" processExpired="false" enableAudit="false"/>
                            <sharedDeadLetterStrategy processExpired="false" enableAudit="false"/>
                        </deadLetterStrategy>
                        <networkBridgeFilterFactory>
                             <conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true"/>
                        </networkBridgeFilterFactory>
                    </policyEntry>

• I don't know if this can be fixed with configuration or if it something that needs a fix to clear out brokerPath when it gets sent to the dead letter queue (or retried)