2723544 - "DuplicateMessageException" in PI JMS Adapter scenario

• SAP Process Integration (PI) or Process Orchestration (PO) JMS Sender channel is used in this scenario.
• While the JMS Sender channel tries to process the message from the JMS queue, it fails with the following exceptions:

Message ID ID:[JMS Message ID] already exists in database: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (UNKNOWN.obj#=171337) violated

OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]

[EXCEPTION]
com.sap.aii.adapter.jms.core.channel.filter.DuplicateMessageException: Duplicate message received with jms message id: ID:[JMS Message ID], xi message id: [XI Message ID]
at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:339)
at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:248)
at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:171)

XI message with ID [XI Message ID] already exists for JMS Message ID : ID:[JMS Message ID]

• SAP NetWeaver
• SAP Process Integration

Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, XI, AEX, JMS,JMS queue,DuplicateMessageException, transaction,EnhancedDuplicateKey  , KBA , BC-XI-CON-JMS , JMS Adapter , Problem