Messages stuck in QRFC inbound and outbound queues by system error

[Former Member]

Hi Experts,

We faced a big problem in our PI server which stopped all the traffic in the iDoc to File interface. Both the QRFC queues (inbound - SMQ1 as outbound - SMQ2) where stuck by a system error.

In IDX5 of PI we saw two inbound iDocs on exact the same date/time of creation. Both iDocs are displayed in SXMB_MONI with the status "Canceled - Since Already Processed". The output files of both iDocs are generetad on the outbound side.

The output files are genereted with a date/time stamp in filename exactly as: "pi_20101106-221812-437.dat" and "pi_20101106-221812-438.dat". So it seems that both processes where running on exact the same time.

When looking into the system error we see the following details:

com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 00505697-181b-1ddf-babd-68f1ac208528(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: [200]: Duplicate key

This caused that the QRFC queues where both stuck in inbound as outbound with a SYSERROR, so PI stopped and the queues should be reactivated manually.

Does anybody have some idea of the real cause of this error. We really want to prevent such situation in the future.

Thanks in advance!

Best regards,

Joost

[udo_martens · Accepted solution]

Hi Joost,

you should consider to schedule reports RSQIWKEX and RSARFCEX. Have a look to Naveen's blog [XI : How to Re-Process failed XI Messages Automatically|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2728] [original link is broken] [original link is broken] [original link is broken];

Regards,

Udo

[Former Member · Accepted solution]

Thanks for your reply Udo. This will definitely help us to automaticly restart the process again when a same situation happens again.

Maybe any idea about the duplicate key error (the cause of the error)?

Best regards,

Joost

[Former Member · Accepted solution]

Hi Joost,

Are you using an adpater module to avoid the same file name processed by the receiver channel ???

If this is the case change the filename and retest flow otherwise remove the module (ex: localejbs/AF_Modules/MessageTransformBean - Local Enterprise Bean) from the channel check it whether the file getting processed or not...

OR...you have an incorrect module configuration in the receiver channel.

Do not remove the standard SAP module and make sure that you add additional modules before it.

cheers,

Ram.

[Former Member · Accepted solution]

Dear Ram,

Thanks for your answer.

We are usering a normal receiver file Communication Channel. The file name is build with the File Constructon Mode: "Add Time Stamp".

So no futher modules are used, only the standard CallSapAdapter.

Could the time stamp in the file be a reason of our problem?

Best regards,

Joost

[Former Member · Accepted solution]

Hi Joost,

Did you found resolution to this problem. I m facing the same error for duplicate check & I am using standard SAp features only, no extra adapter modules.

Any inputs from yourside will be helpful to me.

Kind Regards,

Abhijeet.

[Former Member · Accepted solution]

Hi Abhijeet,

No the problem is not resolved yet but also didn't occurs more the one time yet.

We are using standard SAP features (iDoc to File scenario) from PI to.

Best regards,

Joost