Proper MessageId in sys$scheduler - duplicates in target queue

[trichter]

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

[IIT Software]

You're right, the JMS message id should be unique. It's not possible to send the original id because the message is send on a schedule and thus could be send multiple times so you would have the same problem.

We need to patch that and provide a fix in the next release. Send an email to [e-mail] and I will send you a patch of the sys$scheduler.jar (base 7.5.2).