@stevebu thanks for sharing that great news about a copy.
I want to give you feedback to get into the reality problems customers faces which will show this util need to be extended.
1.) Currently it is just to copy a single message
I would like to see a possibility to:
Copy all Copy all message in certain time range (e.g. messages stranded today there) - the time range filter i would like to see a swell on purge or delete message command. Imagine you have messages in DMQ and they could not get resolved and so you want to just remove them after n days as no reason to resend 2.) The documentation of copy command does not really tell about handling of DMQ Eligible
As it mentions this use case i hope it changed DMQ Eligible back to “true”. As i turns from “true” to “false” on move to DMQ. Honestly i never understood why that is done. It avoids what some people if thought of to set-up DMQ with main queue as Dead Letter to have an automated way every e.g. 1 hour to push messages back from DMQ to main queue. (without any need of copy)
3.) Solace must clarify how the delivery-count is handled in a copy back from DMQ to main queue.
I see 2 options. The delivery-count increases further where it was before it ended in DMQ.
So if there was a 10 retry you reach DMQ with delivery-count 10 and on next push and end again in DMQ you would have already 20. Or you even introduce an additional dmq-delivery-count