Issue with PI messages in "To be Delivered" Status

[RautVinit]

Hello Experts,

We have a Mail to SOAP scenario on PO 7.4 single stack PI system. Currently we are facing issue with messages where messagess are in status "To be Delivered". Messages dont get processed further.

Two days back, we had issue with file system table overflow and this cause messages remained in "Delivering" status. I can see Audit log with error emssage for table space full.

I couldnt cancel/resend those messages.

I believed these messages are causing rest of the messages to go in "To be Delivered" status. I found few blogs to check resources in Java Engine Additional Data->Queues and its looks good.

we had system restart and these "Delivering" messages were cancelled but again when we tried a fresh run and first message went into "Delivering" Status with 500 server error message in audit log and subsequent messages started going into "To be Delivered" status. This is happening only for one scenario, rest of the message are working fine.

I tried wit new BS, Channel, Integrated scenario for same functioanlity but its not working.

Recent messages with "To be Delivered" can be seen with below audit log

Information MP: processing local module localejbs/sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean

Information Mail: Calling the module processor for channel CC_Sender_V2

Information Mail: Message leaving the adapter (call)

Information Trying to put the message into the send queue

Information Application attempting to send an XI message asynchronously using connection AFW

Information Message successfully put into the queue

Information Trying to put the message into the send queue

Information Mail: Call completed

Information Message successfully put into the queue

Information The application sent the message asynchronously using connection AFW. Returning to application

Information Mail: Call returned for channel CC_Sender_V2

we have latest patch(SAP_XIESR Version 1000.1.70) applied 10 days back only

Kindly suggest.

[RautVinit]

Hi All,

Thanks for your reply and suggestions.

Now messages are flowing properly. Issue was with data population in the target structure. Receiver side we have Knowledge Management portal website and CreateDocument operation fields were expecting some values to be populated. We tried few combinations and it worked.

We also tried changing mapping and we could reproduce messages with "To be delivered" status.

Now we are searching for KM Portal Webservice documentation where information about every field of operation is mentioned. If we straight away pass source mailbody to webservice, its not working. failing at webservice end with error 500 internal server error. It expects data to be in Base64 format and also fields like Length of data to be populated. If we get documentation then things would be more easy. We are also passing attachment but its not getting generated at target end. We are not sure if webservice support that feature.

Thanks,

Vinit.

[jyothi_anagani]

Hi Vinit,

Please check this blog.

In addition to that you can try these

1. Give the wrong channel parameters(user name or password) in communication channel and start and stop the channel

2. Try by giving Timeout Parameters.

3. Check for the same interface if any other messages are stuck with system error(Check by Queue) and cancel those messaages and then it will automatically processed

Thanks

Jyothi A

[naveen_chichili]

Hi Vinit,

Go to your url http://host:port/MessagingSystem and check if you have any messages in EOIO queue and try to reprocess those messages.

Thanks and Regards,

Naveen

[iaki_vila]

Hi Vinit,

Check this wiki Messages stuck on Integration Server - Process Integration - SCN Wiki, Im not sure if in PI 7.4 the java options are in the same place

Regards.

[former_member182455]

Hi,

kindly check the Queues in PI system.

Regards

srinivas

[claudia_liszy]

Hi Vinit,

is your scenario Exactly-Once-In-Order? This would explain why the subsequent messages are on hold because the first message has failed. For this case if you solve the error for the first message, all other message will hopefully go through.

Regards

Claudia