This is related to HORNETQ-598.

Consider the scenario where a message (with _HQ_DUPL_ID set) is sent to "queue/A". This message is consumed by a client, but consumption fails such that the message is moved to a DLQ. Now an administrator sees the failed message in the DLQ and invokes "moveMessage" to move the message back to "queue/A" in an attempt to have the client consume the message successfully. Before the fix to HORNETQ-598 the message would get "stuck" in the DLQ. After the fix to HORNETQ-598 the message will not get stuck, but it also won't make it back to the original destination.

HornetQ needs to handle this scenario so that the failed message can be moved back to the original destination.