Skip to Content
0

SAP-XI XML Message status have changed to “Cancelled – since already processed” after SP upgrade

Nov 08, 2016 at 11:06 AM

159

avatar image
Former Member

Hi Experts,

A new error description started appearing in XI system after the SP upgrade as shown below and same description appearing in all XML's with irrespective of message status like success, failure and "Cancelled – since already processed" .

Error description:

<SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code> <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID 581b7c0f-9927-9805-e100-8000ac130c39(INBOUND) already exists in database: com.sap.sql.DuplicateKeyException: [SQL0803] Duplicate key value specified.</SAP:AdditionalText>

if any one encounter this issue, Please let me know that why are we getting this status?. and these records status as processed successfully before upgrade the service pack and I found the error description when I checked the XML's message after upgrade the SP.

Thanks,

Srinivas

10 |10000 characters needed characters left characters exceeded
Former Member

Hi,

Please see the below PI-RWB error for the above mentioned issue(SXMB_ MONI).

09.12.2016 12:16:15.203 Success Message successfully received by messaging system. Profile: XI URL: http://XXXXX(User): XXXXX09.12.2016 12:16:15.560 Success Processing child message of multi-message with message ID XXXXXXXXXX09.12.2016 12:16:15.565 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.09.12.2016 12:16:15.582 Success Message successfully put into the queue.09.12.2016 12:16:17.247 Success The message was successfully retrieved from the receive queue.09.12.2016 12:16:17.249 Success The message status set to DLNG.09.12.2016 12:16:17.252 Success Delivering to channel: CC_SAP_to_Legacy_RCV09.12.2016 12:16:17.252 Success MP: Entering module processor09.12.2016 12:16:17.252 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean09.12.2016 12:16:17.253 Success SOAP: request message entering the adapter with user J2EE_GUEST09.12.2016 12:16:17.253 Success SOAP: Target url: http://XXXXXX09.12.2016 12:16:17.540 Success SOAP: completed the processing09.12.2016 12:16:17.540 Success SOAP: sending a delivery ack ...09.12.2016 12:16:17.540 Success MP: Leaving module processor09.12.2016 12:16:17.540 Success SOAP: sent a delivery ack09.12.2016 12:16:17.540 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.09.12.2016 12:16:17.570 Success The message status set to DLVD.09.12.2016 12:18:47.658 Success Message successfully received by messaging system. Profile: XI URL: http://XXXXX(User): XXXXX09.12.2016 12:18:48.118 Success Processing child message of multi-message with message IDXXXXX09.12.2016 12:18:48.121 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.09.12.2016 12:18:48.126 Error Putting message into receive queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID XXXXXX (INBOUND) already exists in database: com.sap.sql.DuplicateKeyException: [SQL0803] Duplicate key value specified..09.12.2016 12:18:48.331 Success Message successfully received by messaging system. Profile: XI URL: http:/XXXXX(User): XXXXX09.12.2016 12:18:48.337 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.09.12.2016 12:18:48.342 Error Putting message into receive queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID XXXXX(INBOUND) already exists in database: com.sap.sql.DuplicateKeyException: [SQL0803] Duplicate key value specified..

Please let me know if any one have already faced the same.

Thanks,

Srinivas P.

0
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Raghuraman S Nov 08, 2016 at 11:13 AM
0

Hello Srinivas,

What is the scenario?is it happening for all the messages?

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Raghuraman,

It is happening for all interfaces which are coming from SAP.

Thanks,

Srinivas.

0

Hello Srinivas,

Try restarting the Server and check.

0
avatar image
Former Member Nov 11, 2016 at 09:37 AM
0

Hi Raghuraman,

There were many restarts done after SP upgrade and also there are two error messages frequently occurred for SAP to PI system interfaces as shown below.

1)Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)

2)com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID XXXXX(INBOUND) already exists in database: com.sap.sql.DuplicateKeyException: [SQL0803] Duplicate key value specified”.

The above errors are found after SP upgrade only where the same interface processed successfully. Please let us know is there any problem with SP upgrade?.

Thanks,

Srinivas.

Share
10 |10000 characters needed characters left characters exceeded
Shahid Ahmed Khadri Dec 12, 2016 at 02:43 PM
0

Hi Srinivas,

Were these messages already processed successfully before upgrade? If yes, why are these being re-processed again? Also, please filter for which adapters this issue is occurring.

Regards,

Shahid

Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Shahid,

Thanks for your reply.

Yes, all messages were processed successfully before upgrade and after upgrade also and there is no problem with the data as well since very fast time XML processed successfully but the same message processing again which leads the issue.

all SAP to PI directional interfaces getting this issue.

Thanks,

Srinivas.

0

Hi,

Why do you want to process the message again when it has already been successful? That will create duplicate and it doesn't get updated. Try to send fresh messages and see if they are being processed.

0
Former Member
Shahid Ahmed Khadri

Hi Shahid,

Thanks,

we are not resending any messages, system behaves likewise after upgrade the SP and that's what is our issue.

let say if we processed 100 XML's, All XML's are being processed successfully and then after system throwing the error for few messages out of 100 as mentioned above.

Thanks,

Srinivas.

0