Skip to Content

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

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on Jan 30, 2015 at 11:55 AM

    Hi,

    Have you tried to STOP & START communication channel?

    Regards,

    Dipen.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 30, 2015 at 11:56 AM

    Hi Suman,

    Please check sap

    Note 1361305 - File sender adapter generates duplicate message IDs.

    regards,

    Harish

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

  • Posted on Jan 30, 2015 at 12:07 PM
    -1

    Hi,

    Refer to this link,

    Regards,

    Dipen.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.