SAP Knowledge Base Article - Preview

2723544 - "DuplicateMessageException" in JMS scenario

Symptom

JSM 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]


Read more...

Environment

  • SAP NetWeaver
  • SAP Process Integration

Product

SAP NetWeaver 7.1 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

Process Integration, PI, Process Orchestration, PO, NetWeaver, XI, AEX, JMS, DuplicateMessageException, transaction, , KBA , BC-XI-CON-JMS , JMS Adapter , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.