Disable the duplicate check in SAP PI n sender JMS adapter is it possible?

[Former Member]

Hi experts,

My interface is JMS to PROXY (INOUND to SAP). Here WMQ is sending message as:

If the message have multiple records this message is splitting into multiple files based on records (Eg: a message have 40 records it will split into 40 files this is as per requirement) with same message ID. If all messages will coming with same message id except 1st one remaining getting failed in sender JMS adapter because all messages with same Message ID.

Then I am getting below error:

A duplicate JMS message was received. It was received earlier and processed with the XI message ID ed6194a5-9a09-48e9-0dcc-8b52682d1c0d. It will be ignored and discarded from the JMS queue.

In sender JMS channel I am using Time period for duplicate chek = 480000 but it is not working.

Any possibility is there in PI for disable duplicate check.

Please give your valuable suggestion on this

Thank you

Srinivas

[Former Member]

Hello Srinivas,

Just some further information in addition to Saurabhs reply.

It is not recommended by SAP to go without the duplicate check. Doing so would violate the JMS 1.1 specification.

Kind regards,

Sarah

[Former Member]

HI Srinivas ,

First to get rid of the error you have to remove the duplicate messageID from the database by going to table "XI_AF_SVC_ID_MAP" and delete the line according to the PI/JMS message id .Secondly to avoid this error in future you have to tell MQ team to send unique messageid in their MQ header when they are posting message to SAP . Last but not the least if they will keep on sending same messageID in thier MQ header then its bound to throw the error in JMS channel we can't do much in PI for this .

Regards,

Saurabh

[Former Member]

Hi Srinivas,

Can you please check the processing tab of JMS sender channel.

JMS settings

check the transactional JMS settings check box

Delivery mode: Persist JMS messages in the JMS Provider

JMS message expiry: -1 msecs

JMS message Priority :-1

Correlation Settings

Set JMS Correlation iD: PI message ID

PI settings as follows

Mapping message: Message Payload=JMS payload

Handling of Pending PI messages: Throw exception (message Retry possible later)

Time period of duplicate check for EO(IO):86400

Error handling

Wait after Message error : 1000 msec

Wait before reconnect: 1000 msecs

Also in the advanced tab make sure you are adding CONNECTION_TEST_POLL=true

Please check SAP Note:1086303 also.

[Former Member]

Hi,

As you mentioned above parameters.. but below parameters are not salable in my Sender JMS channel.

JMS message expiry: -1 msecs

JMS message Priority :-1

Handling of Pending PI messages: Throw exception (message Retry possible later)

Thank you

Srinivas

[Former Member]

Hi,

It is fixed.. MQ is Sending messages with different message ids

[Former Member]

Hi,

It is fixed.. MQ is Sending messages with different message ids