JMS Adapter Duplicate Message ID Problem

[Former Member]

Hello all,

We are currently having a problem with our JMS adapter from a specific queue.

MQ --> JMS --> XI

MQ is sending us a JMS Message but the Message ID for all the message is exactly the same. This throws the XI exception to check for duplicate message. And the message sits in the table until we us a workaround we have implemented to delete the old message so the new one can process. We need a different work around because the message just stack up and can be delayed up to 5 days because of the duplicate JMS Message ID. The MQ people have opposed the idea of sending unique JMS Message IDs.

Any help is greatly appreciated.

Thanks

Chirag

[Former Member]

Hi Chirag, did you ever find a root cause / solution to this issue?

[JaySchwendemann]

Hi Aaron / all,

I saw you posting on at least 2 threads about that time. We have similar situation now with 3rd Party --> MQ --> PI --> ERP. We're on PI 7.4 SP 7 AEX.

I lately fondled with "Message Receive Wait Time" and put it from 100 to 1000 msec. However, as we cannot reproduce in Test we'll have another go at the end of the week.

Rest of the adapter is configured like so:

How did you solve your issue back then?

Many Thanks

Cheers

Jens

[Satyagadadas]

Did you try by putting "-1" in Time period for duplicate check and

set XI message id to "GUID"

[Former Member]

Yes we have tried that, that doesn't work. The problem is occuring from the source program, so there isnt much we can do from XI.

[Former Member]

Wow... You take almost a year to reply!!!