com.sap.sql.DuplicateKeyException in file receiver channel

[Former Member]

Hi experts,

I am currently testing the following scenario:

xml file -> file sender ->file receiver -> csv file

No mapping is used. Both channels are on the same PI 7.1 system.

The transformation seems to work so far. The only problem I have is that my receiver channel does not post the message to the directory because of this error:

Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id f167e134-145e-4b2c-2d47-e431b8b34fd8(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: [200]: Duplicate key.

Is it not possible to use file sender and file receiver in the same scenario? Thanks for any help.

Best regards.

Oliver.

[former_member4985 · Accepted solution]

Hello!

This seems to be due to the incorrect module configuration in the receiver channel.

Kindly correct the same and retry your scenario.

Regards,

Caio

[Former Member · Accepted solution]

Hi,

this is my module configuration.

Transform.Class - com.sap.aii.messaging.adapter.Conversion

Transform.ContentType - text/plain;charset=utf-8

xml.addHeaderLine - 0

xml.conversionType - SimpleXML2Plain

xml.endSeparator - 'nl'

xml.fieldSeparator - ;

Well, if there is an error please let me know.

Best regards.

Oliver Barnert.

[stefan_grube · Accepted solution]

which are the modules in your channel?

[Former Member · Accepted solution]

I have only one module:

localejbs/AF_Modules/MessageTransformBean - Local Enterprise Bean

Best regards.

Oliver.

[stefan_grube · Accepted solution]

> I have only one module:

> localejbs/AF_Modules/MessageTransformBean - Local Enterprise Bean

That's that reason. Just what Caio mentioned.

You must not remove the standard SAP module.

Add additional modules before it.

[Former Member · Accepted solution]

Thanks Stefan, now it works perfectly.

[balaji_pichaimuthu]

HI,

I belive there is a adpater module which is avoid the same file name processed by the receiver channel. And i think there is table which is having all the filenames already processed.

If this is the case change the filename and retest flow otherwise remove the module from the channel check it whether the file getting processed or not

Regards,

Balaji

[Former Member]

Hi Oliver,

do you have transferred the same message twice (without archiving & deletion)?

That could be the reason.

Just put a new file into you source directory and try again.

Cheers,

André

[Former Member]

Hi André,

I am using the test option so the message can be processed multiple times. Anyway, I also tried using deletion but I still get the same error. I also tried a completely new file but still no change. When I check the comm channel I see that there is always created a new message id and when I search the rwb it posts two entries. One from the sender step and one from the receiver step. Seems to be alright to me.

Regards.

Oliver.

[stefan_grube]

There is nothing wrong, I always do this the same way.

It is a bug. Check for OSS tickets or apply the lastest SP.

[stefan_grube]

> Is it not possible to use file sender and file receiver in the same scenario?

Sure you can. This is not the reason for your issue.