cancel
Showing results for 
Search instead for 
Did you mean: 

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

0 Kudos

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,

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member182412
Active Contributor
0 Kudos

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.

former_member190293
Active Contributor
0 Kudos

Hi Getinet!

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

Regards, Evgeniy.