Messages are in to be delivered status

Many messages are in to be delivered status in the adapter engine message monitoring
Can any body help regarding this

Hi Sandeep,
     Would you explain a little bit more your issue?
     i.e:
     This kind of messages are Sync Messages?
     Do you have more than one message in Interfaces Determination object?
     If multiple inbound interfaces are assigned by the interface determination, the messages are forwarded according to the quality of service Exactly Once in Order (EOIO) at runtime. This means that the order in which the inbound interfaces are entered in the interface determination determines the order in which the messages are received.
     You can change this default by deselecting the Maintain Order at Runtime checkbox. In this case, the quality of service Exactly Once (EO) is used to forward the message to the inbound interfaces.
Regards,
Luis Diego

Similar Messages

Messages are in Backlog without any status

Hi All,
Today morning when I came and observed that, in the Engine-Status page i saw some 3000 messages under column
"Processing Backlog (without errors)". When I went into Messaging Overview Tab, I see these messages are in 'To Be Delivered' status. Now How to reprocess these messages? Can anyone tell me how come out from this situation?
Regards,
Rahul

Hi Achaari,
This is related to Queues problem.U r messages are struck in Queues.Please do following steps.
1)Go to SMQ2.Then check ur queues.if u found any queues just select it and activate the queue.It will automatically sent the data.
2)Go to SXMB_ADM->Manage Queues->Register Queues->Activate Queues.Before doing this activity in SXMB_ADM please delete or activate the queues in SMQ2 other wise it will give error.
3)Cancel the System Error Messages in Adapter engine in RWB Message Monitoring.
4)Refresh Cache Objects SXI_CACHE.
Thanks
Ravi

Messages are in to be delivered state and slows down the message processing

Hello,
Messages are in to be delivered state and slows down the message processing.
this happenens in case of DB2 on some machine where the issue about high load on DB2 is caused by standard programming in SAP XI that executes a statement, where it uses the condition 'where 1<0' prio to the original SQL statement configured in the channel configuration,
Can you please help me out in solving this issue?
Thanks,
Soorya

Status: TO_BE_DELIVERED
Which 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.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
1. Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
2. We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords

Messages stuck in TO BE DELIVERED status

Hi !
Suddenly, whenever a message has to use the File Adapter, no mather which communication channel is to be used, the message is stuck with the "TO BE DELIVERED" status.
These messages, all have SUCCESSFUL status in the SXMB_MONI. The problem is in adapter engine. ALL have NO errors in their Audit Log. Because the problem is in adapter engine/framework, obviously queues at SMQR/SMQ1/SMQ2 are emtpy. ALL have QoS = EO (no eoio queue is used, NO predecessor messages are stuck with system error).
This occurs no mather which adapter is the sender (RFC, File, etc.)
The audit log is:
2008-04-10 16:59:34
Success
Message successfully received by messaging system. Profile: XI URL: http://xxxxxxx:yyyyy/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-04-10 16:59:34
Success
Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-04-10 16:59:34
Success
Message successfully put into the queue.
If we try to resend the message using the "resend" button in RWB, the message keeps in the TBDL state and the only difference is a new "success" entry in the audit log saying that:}
"Success | Admin action: Trying to redeliver message".
We already refreshed the cache and restarted the Java stack.
Any clues?
Thanks !
Regards,
Matias.

Hi,
Statuses such as HOLDING or FAILED usually happen only for delivery semantics EOIO (exactly once in order) or BE (best effort means Asynchronous). TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue. This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
The MS returns HTTP 200 to the Integration Server only if this was executed successfully. In this example scenario, status TO_BE_DELIVERED should not appear since we assume that the IS has called the servlet successfully.
The status is updated from TO_BE_DELIVERED to DELIVERING when the message has popped out of the receive queue and the event handler lookup was successful, so there is a small gap where TO_BE_DELIVERED could remain in the message monitor, although it was delivered from IS successfully.
Regards,
Srini

Messages are in To be delivered state in the Adapter engine

Hi,
For all the receiver file adapters the messages are successful processed through Integration Engine ,no messages are stuck in SMQ1 & SMQ2 on Inegration engine.
All the messages are stuck in Adapter Engine with the status "To be Delivered ". These are all asynchorus scenarios. The quality of service is also EO.
We restarted the J2EE engine also several times but no luck.
Did anyone had similar issue?
Thanks
Sachin

Hi,
Status: TO_BE_DELIVERED
Which 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.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords and tcode - SXMB_ADM and "active" the queue then the messages and check it out.
Regards
Agasthuri Doss

Trigger Alert E-Mail When messages were in To Be delivered Status

Hello all,
Is it possible to trigger an Alert E-mail if a message struck up in 'To be delivered' status ??
I Know this status is not an error status with AE to trigger alert automatically. We are facing this problem often and when we restart XI AF messaging system, all messages were processed.
We would like to know if messages were struck up with that status more than 15mins.
Any thoughts??
Regards

Hi,
Standard Alert Frame work will not support sending an Alert for To Be delivered status.
you have to do some work around,
check below blog and apply this design
/people/shweta.walaskar2/blog/2011/05/12/trigger-alerts-for-messages-in-to-be-delivered-status-monitoring-adapter-queue-lock
Regards,
Raj

Messages are in "To Be Delivered" state

Quite many times has happened that several messages have been stucked in XI 7.0 Production system in status "To Be Delivered".
Resending stucked messages is not possible.
The solution for issue is to restart Java stack.
But This is not permanent solution to restart Java stack of production system every time.
Please guide me to resolve this issue.

Hi Rohan,
In the Adapter engine message monitoring please enable the serialization context and check is there any old message is in error or holding or waiting status.
If there is any please cancel them and resend the TBDL message.
Thanks and Regards,
Murugavel S

Messages are not actually being delivered.

I only have this issue with a single friend. We send messages and they are labeled as delivered but we never receive the message. We get something like 2-3 out of 40-50 texts "sent"

http://support.apple.com/kb/ts2755

Messages are in schedule state

Hello all,
I done flat file to flat file scenario. In sxmb_moni error showing "scheduled flag for my interface". If i went transaction SMQ2 click on display button then messages are going to showing the status: schedule for out outbound processing. In message monitaring messages are in To Be Delivered status and Waiting Status. If i resend those messages, status are not changing. Please help me out from this problem.
Thanks

Hi,
chk in SMQ1 and SMQ2 and delete the entries .
if your queue is registered as inbound and outbound.
also chk in SMQR if ur queue is registered as Inbound or Outbound
reward points if helpful...
PrashaNt

Messages are in "To Be Deleivered ". State

Dear Experts,
We are getting the following error in RWB ,Adapter monitoring which made All the messages are in "TO BE DELIVERED" status.
Please suggest any ideas to resolve the same which can be rewarded accordingly...
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection *** after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND)
Thanks,
Kiran.

Please see the more error information as follows ..
==== Events on Server ******** ====
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection RNIF11_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection SFTP_http://seeburger.com/xi after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection Split997_http://seeburger.com/xi after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection RFC_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection JDBC_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection RNIF_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection SOAP_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection Marketplace_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection CIDX_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection AS2_http://seeburger.com/xi after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection BC_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection JMS_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection Mail_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/AFWListener could not be created for connection File_http://sap.com/xi/XI/System after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:27)
Adapter Engine, message: Fatal Message listener localejbs/RNIFMessageListener could not be created for connection RNIFAdapter after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 08.09.2008 07:39:26)
Adapter Engine, message: Fatal Message listener localejbs/MarketPlaceAdapterListener could not be created for connection MPA after 60 attempts.
Thanks,
Kiran.

'To Be Delivered' status in DAE; Issue with DAE?

Hi,
We have Decetral Adapter Engine (DAE) in DMZ. When we use DAE to drop file using receiver file/FTP adapter, we see all the messages are in "To Be Delivered" status.
Sender file/FTP adapter is able to pick the file succssfully from the same location.
Audit log has the following status:
Success Message successfully received by messaging system. Profile: XI URL: http://sapxaqv:52100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
Success Message successfully put into the queue.
We tried to change all the parameters in receiver CC, still the same status as 'to be delivered' even after giving few wrong parameters to test (gave worng password didn't detect it). Looks like it doesn't going beyond the queue to process.
Thanks for your help in advance.
Thank You,
Indrasena Janga

Hi,
Generally "to be delivered" status messages cannot be changed to any other status directly except by taking the restart of messaging service in the Visual Admin.
Goto Visual Admin --> AF (Adapter Framework) services and take a restart of this particular service.
J2ee Restarts sometimes helps but this aint a recommended or feasible option.
Up gradation to SPS18 would be helpful to avoid restarts.
Cheers
Dhwani

Messages are hanged in "Delivering" status

Hi everyone,
I have an IDoc -> PI -> File scenario. Everything works fine until the message reaches the file adapter. In the Communication Channel monitoring there is no activity for that message, and the channel is correctly configured and started. However, in the Message Monitoring, when I filter for my receiver interfacce, I see that there are 4 messages that have been in "Delivering" status for 2 days. Then, there are a lot more messages in "To Be Delivered" which I guess are waiting for the first ones to finish.
I stoped & started the channel, I tried to resend the messages and nothing happened. Any suggestions? Thank you very much!
Regards,
Pablo

Hi Pablo,
"However, in the Message Monitoring, when I filter for my receiver interfacce, "
--- First Remove all the filters in the RWB,
now set the status filter as "System Error" and select the date range for more than six months or 1 yr ...
now if you see any message then delete them,
Again set the status to "To Be Delivered" and delete all of them.
now set the status to "Delvering" and restart them,
this is what i do when ever i face this problem.
Regards,
Karna...

Stuck in To Be Delivered Status in Message Monitoring - Adapter Engine

Hi,
I have messages stuck in To Be Delivered status in Messages Monitoring. When i checked the Audito Logs, there are NO LOGS. I resent the message and now the logs indicated in the Audit Logs is:
2014-03-26 08:39:10
Information
The message was successfully received by the messaging system. Protocol: XI URL: http://<host>:<port>/MessagingSystem/receive/AFW/XI Credential (User): PIIXXXX
2014-03-26 08:39:10
Information
Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2014-03-26 08:39:10
Information
Message successfully put into the queue.
2014-03-26 08:52:48
Information
Admin action: Trying to redeliver message.
The connection between the receiver is ok, does this have something to do with the Communication Channels?
Please help.
thank you.

Hi Eng Swee,
there are messages that were cancelled yesterday and the status is 'Terminated With Errors'
this is what is indicated in the Audit Logs
2014-03-26 02:38:47
Information
Admin action: Trying to fail message.
2014-03-26 02:38:47
Error
The message status was set to FAIL.
2014-03-26 02:38:47
Information
Admin action: The message was successfully set to status failed.
2014-03-26 02:38:47
Error
Asynchronous error detected: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Message failed by admin.. Trying to report it.
2014-03-26 02:38:47
Error
Asynchronous error reported.
Is this the reason why the messages are stuck?
thank you!

PI RWB-Messages stuck in Delivering Status

Hi Experts,
PI 7.1
Scenario: Proxy to Mail (Outbound)
QOs: Exactly Once in Order
We are facing problem while sending messages to receiver.
Messages are stuck in Delivering status and the messages followed by them are going into holding status.
Messages in Delivering status has no audit logs.
Issue has started couple of months back. We took restart initially to rectify the barrier but it is happening again. This is repetitive issue and we are looking for permanent fix. Restart is not preferred resolution as it is a production system. Please suggest how can we overcome it? It would be a great help.

Hi Hardik
I've blogged about this issue recently. Please check out the blog:-
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/03/27/handling-and-preventing-messages-stuck-in-to-be-delivered-status
Rgds
Eng Swee

Messages stucked "To be delivered" and "Delivering" Status.

Hi,
Lots of messages are stucked in Adapter engine with status "To be delivered" and "Delivering" in our production system.
We found out there is some FTP connection problem with one of the interface which runs only few messages per day. Because of the problem of this interface, it is stopping many other critical interfaces to process and all these messages are falling "To be delivered" and "Delivering" status. All these interfaces are running in File adapters but going to different servers.
If there is problem with one server(One file adapter), why is it stopping all the other interfaces to process?
What might be the problem and how to solve it?
PS: As a temporary solution we are solving this issue by restarting the java stack.
Thanks
Deepthi.

Hi,
Check the below SAP Note Q.47
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267
Which talks about the maximum concurrency..which means that the threads can be controlled for a particular adapter..
As you said there are multiple ftp adapters and because of one its affecting all..
To avoid this the maximuum no of threads awarded to one adapter can be controlled so that the remaining threads can be used by other adapters...
For example...
Assume problematic adapter might be running for every 5 min...
Another adapters are running for every half an hour...
Before first run of another adapter , problematic adapter might have run for 5 times and occupies all 5 threads (thread wont get release as it will be in Delivering state...) remaining threads (another adapter threads) will go into ToBeDelivered state...
if you activate above parameters...only the assigned no of threads to particular adapter will be in Delivering (assume no as 2) then there will be 3 threads remaining which can be utilised by other adapters...
HTH
Rajesh

Messages are in to be delivered status

Similar Messages

Maybe you are looking for