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, PI, Process Orchestration, PO, NetWeaver, XI, AEX, JMS, DuplicateMessageException, transaction , KBA , BC-XI-CON-JMS , JMS Adapter , Problem