(1)
note this is an inefficient way of correlating replies to a persistent queue
a consumer will have to be created for each reply message
see testUseMessageIDAsCorrelationIDPersistMultiReplyToWithNamedSelectorMultiNode
or testCorrelationIDPersistMultiReplyToWithNamedSelectorMultiNode
for a faster way to do this. Note however that in this case the message copy has to occur
between consumer -> producer as the selector value needs to be propagated to the ultimate
destination, which in turn will copy this value back into the reply message