Proper MessageId in sys$scheduler - duplicates in target queue

Hallo,

currently we have some issues relating to JMSMessageId being generated along this pattern "ID:sys$scheduler:${JMS_SWIFTMQ_SCHEDULER_EXPIRATION}" for message sent to a destination queue by a message schedule.

This triggers the duplicate detection of our connection factories in some cases, by which we loose message with duplicate ID (which happen to exists in our case).

How can we make the SwiftMQ scheduler use the original message id or some other unique id as message id fro the message in the destination queue of the message schedule?


Best Regards,
Toralf Richter