use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server to move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server to move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server to move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server to move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Doing so, allows the target server to move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a

use-duplicate-detection . This optional parameter determines whether the bridge will automatically insert a duplicate id property into each message that it forwards. Core Bridges 138 Doing so, allows move messages reliable between nodes of the cluster. Consequently they can also be configured to insert the duplicate id header for each message they move using their internal bridges. To configure a