cancel
Showing results for 
Search instead for 
Did you mean: 

TO BE DELIVERED

Former Member
0 Kudos

hi,

we are facing problem in resolving the "TO BE DELIVERED" message status.

went through many forums and most of them are recommending for adapter engine restart.before doing that we checked

SMQ2 is empty and http://<HOST>:<PORT>/MessagingSystem/receive/AFW/XI

is retunring 200 .AIFUSER and APPLUSER are not blocked,cant see any errors in AUDIT log against "to be delivered" message.

moreover in our scenario if one message is set to be delievered the successive messages are all set with the same status "to be delivered".

cheked sxmb_moni and no system failures found.

can any one explain what exactly "to be delivered " is and how can we resolve without restarting adapter engine.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Refresh your cache..

T Code - SXI_ Cache...

Try to send again....

vasanth.

Former Member
0 Kudos

hi Vasanth,

SXI_CACHE reflects the cache refresh of configuration part of XI.

all my channels ,sender,receiver are configured and were working fine,haven't made any changes to them recently,can you please tell me in what way the refreshing xi cache and "to be delivered " are related since one addresss to Integration Engine and the other Adapter Engine

Thanks & Regards,

Rama Krishna

Former Member
0 Kudos

Hi,

refer this thread..

vasanth.

Former Member
0 Kudos

hi vasanth,

cant find the relation between SXI_CACHE and to be Delivered.

already went through the given thread long back.

that speaks about sxmb_moni,smq2 which were fine at my scenario

Thanks & Regards,

Rama Krishna

Former Member
0 Kudos

Hi ,

I mean that Did you try starting your J2EE Engine again...

vasanth.

Former Member
0 Kudos

hi Vasanth,

we havent restarted engine yet.

this engine problem is not frequent and no clue at audit log.

will restart after some time but we cant restart production everytime we encounter "to be deilvered" and doing so meaningless.

Regards,

Rama Krishna

Former Member
0 Kudos

These may be usefull...

Award points if found usefull.....

former_member214364
Active Contributor
0 Kudos

Hi Rama Krishna,

Exactly where you are getting this message "To Be Delivered"?

did the message passed through Integration Engine or not?

Former Member
0 Kudos

Hi rama krishna !

To_be_delivered means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.

TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.

did you check sxmb_moni_bpe,see if you get any error there for your BPM

also check smq1 and smq2,make sure you dont have any queues stuck there,

What does the audit log say in RWB?

Otherwise you might want to extend the trace file.

You can access the files with the log viewer service of the J2EE Visual Administrator or with the standalone log viewer.

Traces are used to analyze runtime errors. By setting a specific trace level for specific locations, you can analyze the behavior of individual code segments at class and method level. This is done with the help of the log configurator service:

&#61680; Services

&#61680; Log Configurator

&#61680; Locations

&#61680; Choose the location (Java package) and the tracing level (severity)

(for example, com.sap.aii.adapter.file)

&#61680; Root Location > com > sap > aii > File

&#61680; Set the severity and choose Copy Severity to Subtree.

go through the following threads...which already discussed about the same problem

TO BE DELIVERED

://://://

restarting the j2ee engine might also help

Thanks!!!