Skip to Content

massage is delivered to target but channel is trying to send it again

hi

my scenario is working fine which means sender pick file from source and receiver drop it to target directory but am getting the below errors in RWB

Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id e684f539-8eab-11e6-a91c-0000005414ce(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00173403) violated .

Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id e684f539-8eab-11e6-a91c-0000005414ce(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00173403) violated

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 e684f539-8eab-11e6-a91c-0000005414ce(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00173403) violated .

i used custom adapter module to met my requirement

is there anybody to help me what causes those errors?

thanks,

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Oct 14, 2016 at 01:37 AM

    Hi Getinet!

    Try with restarting "XPI Adapter: File" service in NWA.

    Regards, Evgeniy.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 14, 2016 at 03:12 AM

    Hi Getinet,

    Check this sap note

    1979353 - Recurring TxRollbackException with MODE_STORE_ON_ERROR stage configuration

    Prerequisite: the first one or more steps with message storing are configured with MODE_STORE_ON_ERROR in the staging configuration used by scenario.

    Reason: In case of an error while storing the message in DB at the step with MODE_STORE_AND_RETURN (e.g. a DuplicateKeyException) the system will try to store the message once again (for the step configured with MODE_STORE_ON_ERROR) in the same transaction which is already marked for rollback.

    Workaround: A possible workaround is to remove the leading steps with MODE_STORE_ON_ERROR from staging configuration or change the mode to MODE_STORE_AND_RETURN.

    Regards,

    Praveen.

    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.