Skip to Content
author's profile photo Former Member
Former Member

DuplicateMessageExc in Snder JDBC Adapter although succesfull in SXMB_MONI

Hi Experts,

I am getting "com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 5b72a60b-b0e2-48f0-3701-cdb67ac1c5b2(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00149397) violated " as well as "Error during commit or rollback of database transaction: 'com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to commit transaction: The transaction has been rolled back: com.sap.engine.services.ts.transaction.TxRollbackException' in the Sender JDBC Adapter.

The message is processed successfully in ABAP stack . I have stopped and started the relevant Communication channel from RWB however the message is continually processed by the adapter with error. Please assist , how to cancel the message.

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Mar 29, 2011 at 10:49 AM

    This error relates to a JDBC sender adapter on a SAP PI 7.11 SP6 system.

    We have identified a problem with this particular interface. CC_JDBC_Send_FrontOffice_RJ35_NFE_CREATE. A specific message, b72a60b-b0e2-48f0-3701-cdb67ac1c5b2, continues to be sent. SAP PI is then rejecting the message as its unable to commit the record processing to an internal table and rolling back the transaction.

    When checking NWA Java logs we found the following error:

    Module Exception 'com.sap.aii.af.lib.mp.module.ModuleException: senderChannel 'ce6444c858cb3a9baef6b39c35f79106': Catching exception calling messaging system' found, cause: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 5b72a60b-b0e2-48f0-3701-cdb67ac1c5b2(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00149397) violated

    So it appears that SAP PI attempts to update an internal table with the status of the message and fails due to duplicate records. In other words SAP PI knows its already processed the message. This message continues to be sent to the adapter for processing and continues to fail.

    How can we stop this message being procesed?

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 20, 2011 at 09:47 AM

    Hi,

    We have the same issue.

    Any input, please? have you solved this problem?

    thanks, in advance

    Carme.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 20, 2011 at 10:01 AM
    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.