com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException

[suman_saha]

Hello Experts,

We are on PI 7.31 single stack.

We are getting a strange issue for File Sender Adapter(EOIO).

Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 87bc642b-a70a-11e4-8160-000020060e26(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (UNKNOWN.obj#=17503) violated

OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]

When we check in communication channel monitoring, it is showing the same message id in error. But if we check the same message id in message monitoring, the status is shown as delivered and in message log,we can see the above mentioned error.

Please help.

Regards,

Suman

[dipen_pandya]

Hi,

Refer to this link,

Regards,

Dipen.

[suman_saha]

We can't change the file location or the file name as some of the lines are already processed into ECC and we don't afford duplicate records.

[dipen_pandya]

Hi,

Can you please try with below approach,

1. Go to Configuration and Monitoring Home
2. Select your Communication Channel
3. Click on the displayed Message Id
4. In Database tab select that Outbound Message Id (87bc642b-a70a-11e4-8160-000020060e26)
5. Remove that Message Id as shown in below screenshot

Try this if it helps.

Regards,

Dipen.

[suman_saha]

This functionality is only for searching purpose in message monitoring I think, it doesn't have any impact on table.

[dipen_pandya]

Hi,

Any progress! Did you resolved the problem?

Regards,

Dipen.

[suman_saha]

Hi Dipen,

Sorry for late response.

We removed the file from the FTP location, put the file with new name again rectifying the error.

The file was fixed length file, but the length was not proper, so error was thrown during content conversion.

Suman

[oscar_mller]

Hi Dipen,

Where is this Configuration and Monitoring Home ? I am with the same issue. My version is 7.1.

Thank's

[Harish]

Hi Suman,

Please check sap

Note 1361305 - File sender adapter generates duplicate message IDs.

regards,

Harish

[suman_saha]

Hi,

This note is not related to our PI version i.e. 7.31

I also got a note for PI 7.31

My question is even if we apply the patch, will it resolve the current issue or it will prevent same issue in future?

As per the note, the patch will upgrade the message id generation algorithm. But what about the message id which is already generated?

Regards,

Suman

[dipen_pandya]

Hi,

Have you tried to STOP & START communication channel?

Regards,

Dipen.

[suman_saha]

Hi,

This was the 1st thing we did.

We have even restarted the Java Service, afterwards restarted the java engine also.

Regards,

Suman

[dipen_pandya]

Hi,

As in Java Only PI 7.31, SAP Note 1361305 is not applicable.

If you are going to face this problem for long then raise an OSS message.

Can you please provide a screenshots of error in CC monitoring and CC configuration?

Regards,

Dipen.