Broker rejecting MQ message as Duplicate

When creating an MQ asynchronous notification trigger it appears that webMethods uses the msgId from the queue message as its store id.
Here is the problem - The application writing to the queue does not put a unique msgId on each message. (Doesn’t matter why it just does.)
So depending on how many messages are coming into broker and how fast the process can keep up, some messages will be disregarded as duplicates.

Does anyone know where you can explicitly tell webMethods not to use the mq msg Id, but to generate a unique Id? Or ignore the fact that it
appears to be a dupe by the mq msgId. Also, the problem seems to be in the step that puts the message on broker not the trigger service
that subscribes. The subscriber is set not to detect duplicates (false).

The log dump below demonstrates what happens. Any line with the verbage …MessageType ==> … was successful. There were 5 messages sent to a queue.
The bottom section is when the msgId is not unique. As you can see only 3
messages were processed – 2 discarded. The top section is the exact same messages with unique msgId’s.

 [316]2008-03-13 16:22:51 EDT [ISP.0090.0004I] ObCwResources.External:putCw101AuthCcIn -- MessageType ==> Send
[315]2008-03-13 16:22:51 EDT [ISP.0090.0004I] ObCwResources.External:putCw101AuthCcIn -- MessageType ==> Footer
[314]2008-03-13 16:22:50 EDT [ISP.0090.0004I] ObCwResources.External:putCw101AuthCcIn -- MessageType ==> Summary
[313]2008-03-13 16:22:50 EDT [ISP.0090.0004I] ObCwResources.External:putCw101AuthCcIn -- MessageType ==> Detail
[312]2008-03-13 16:22:49 EDT [ISP.0090.0004I] ObCwResources.External:putCw101AuthCcIn -- MessageType ==> Header
 
 
[311]2008-03-13 16:13:50 EDT [ISP.0090.0004I] ObCwResources.External:putCw101AuthCcIn -- MessageType ==> Send
[310]Rejecting document as there is no enabled Trigger registered: ObCwResources.MQ.Notifications:Cw101AuthCcOutPublishDocument
[309]2008-03-13 16:13:50 EDT [ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ART.116.3010] Adapter 
Runtime (Notification): Error publishing notification ObCwResources.MQ.Notifications:Cw101AuthCcOut. Error: Rejecting document as 
there is no enabled Trigger registered: ObCwResources.MQ.Notifications:Cw101AuthCcOutPublishDocument.
[308]2008-03-13 16:13:50 EDT [ISS.0098.0024C] No Trigger available for incoming Document ObCwResources.MQ.Notifications:Cw101AuthCcOutPublishDocument. Rejecting Document
[307]2008-03-13 16:13:50 EDT [ISS.0098.0082E] Unable to persist Document: ObCwResources.MQ.Notifications:Cw101AuthCcOutPublishDocument to Document Store: 
ObCwResources.MQ.Notifications:Cw101AuthCcTrigger. Exception: com.wm.app.b2b.server.dispatcher.exceptions.DupeMsgException: com.wm.app.store.TSDupeMsgException: 
[BAT.0000.0032] duplicate message for store id ObCwResources.MQ.Notifications:Cw101AuthCcTrigger in parent container id TriggerConsumer
[306]2008-03-13 16:13:49 EDT [ISP.0090.0004I] ObCwResources.External:putCw101AuthCcIn -- MessageType ==> Summary
[305]Rejecting document as there is no enabled Trigger registered: ObCwResources.MQ.Notifications:Cw101AuthCcOutPublishDocument
[304]2008-03-13 16:13:49 EDT [ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ART.116.3010] Adapter Runtime (Notification): 
Error publishing notification ObCwResources.MQ.Notifications:Cw101AuthCcOut. Error: Rejecting document as there is no enabled Trigger registered: 
ObCwResources.MQ.Notifications:Cw101AuthCcOutPublishDocument.
[303]2008-03-13 16:13:49 EDT [ISS.0098.0024C] No Trigger available for incoming Document ObCwResources.MQ.Notifications:Cw101AuthCcOutPublishDocument. Rejecting Document
[302]2008-03-13 16:13:49 EDT [ISS.0098.0082E] Unable to persist Document: ObCwResources.MQ.Notifications:Cw101AuthCcOutPublishDocument to Document Store: 
ObCwResources.MQ.Notifications:Cw101AuthCcTrigger. Exception: com.wm.app.b2b.server.dispatcher.exceptions.DupeMsgException: com.wm.app.store.TSDupeMsgException: 
[BAT.0000.0032] duplicate message for store id ObCwResources.MQ.Notifications:Cw101AuthCcTrigger in parent container id TriggerConsumer
[301]2008-03-13 16:13:49 EDT [ISP.0090.0004I] ObCwResources.External:putCw101AuthCcIn -- MessageType ==> Header