on 08-21-2007 7:49 AM
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.
Hi,
Refresh your cache..
T Code - SXI_ Cache...
Try to send again....
vasanth.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rama Krishna,
Exactly where you are getting this message "To Be Delivered"?
did the message passed through Integration Engine or not?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
 Services
 Log Configurator
 Locations
 Choose the location (Java package) and the tracing level (severity)
(for example, com.sap.aii.adapter.file)
 Root Location > com > sap > aii > File
 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!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.