cancel
Showing results for 
Search instead for 
Did you mean: 

Adapter Level Error To be Delivered

Former Member
0 Kudos
52

Hi Guys,

i got few messages status with status as " To be Delivered" in Receiver Adapter level.

i tried to resend the message from Runtime work bench, its not working.

generally i got this type of status at target adapter level. everytime i did resend the messgaes from runtime workbench it self.but this time its not working fine.

i checked adapter status as well, everything looks good.

can any one pls expalin me how to resolve this issue.

Regards,

Siva.

Accepted Solutions (0)

Answers (3)

Answers (3)

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

Check note #1662269 - How to Monitor the PI Adapter Framework queues. This should let you know if all available threads are stuck. If yes, restart the java node to free the threads.

You may also need to increase the number of queues/threads available to this adapter connection. See these blogs:

1) [Messaging System queue properties |http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7141] [original link is broken] [original link is broken] [original link is broken];

2) [Tuning the PI Messaging System Queues|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22896] [original link is broken] [original link is broken] [original link is broken];

Regards

Mark

Former Member
0 Kudos

Hi,

This can be due to the EOIO QOS for the messages...

Check the messaging system http://host:port/MessagingSystem/ ...here you can see the tab EOIO Sequence monitor...

There you should be able to find the message which failed and as a result another message went into Waiting state..

Once you clear off those messagess ...Message from ToBeDelivered state will be changed..

HTH

Rajesh

former_member184681
Active Contributor
0 Kudos

Hi Siva,

The error you are receiving means that the message is waiting in a queue to be delivered to target system. Reprocessing the message won't change anything in this case. Instead, try checking the status of your outbound queues in transaction smq1. Most probably you will find your messages stuck in a queue behind another message having an error status. Your messages will not be processed in this case, until the queue is unblocked (the message that blocks the queue is either processed or deleted from the queue).

Hope this helps,

Grzegorz