Message in Delivering status

Guys,
How do you stop messages running in scheduled state with status 'Delivering\.
It is been in that status for couple of days.
Am still getting error 239, connection refused from receiver FTP server.
When i checked their log, it was in FIN_WAIT2 status.
Please share light on this.

Hi,
" to be delivered" status may be because of following reasons:
-Receiver is not available
-Queue hang-up: check out SMQ2 for the message queue status
-try to restart the messages from the RWB-->Message Monitoring
-try out the accessibility of NFS folder from the PI server
-Re-activate the Receiver file channel with Receiver agreement..
for more on the Adapter Engine log, you can check this from the Visual Admin- log files
Regards
Aashish Sinha
PS : reward points if helpful

Similar Messages

Adapter Engine Message in Delivering Status

Hi All,
Any idea how to cancel/delete the messages which are in delivering status in Adapter Engine.
In my case a single EOIO message is stuck in the AE with delivering status. Other messages are flowing successfully using the same cc.
Earlier during such cases we had to restart j2ee/ stop/start AF Messaging to resolve the problem.
Just wondering if theres any other solution?
btw : The message was in delivering status because the password mentioned in the receiver channel was wrong. There were other messages which failed but the status of those messages went into "System Error". Nothing wrong with that, but just wondering why did a single message remain in the "Delivering" status.
I have already been through this thread Re: How to delete message in "Delivering" status. Only exists in Adapter Engine and didnt find/understand anything which could help me.
Thanks
Sumit

Look at these blogs,
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework : How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
XI : How to Re-Process failed XI Messages Automatically
Message stuck in Adapter Engine queue with status "Delivering"
Hope this helps

EO Messages with Delivering Status in Adapter Engine

Hi All,
We have a scenario DB-DB Asy with Java Proxies. Proxies are there to accept the messages from Sender DB and insert in target DB. Get the response from target DB and insert back that to Sender DB.
Actually the scenario is Syn, but we made it as Asynchronous by implementing Java Proxies.
Now we are using EO mode in Sender JDBC channel. We have 17 interfaces in the similar pattern. We are using one common XI receiver channel for all these 17 interfaces.
If one message got struck, then rest other Proxies are not getting triggered and not able to resend the message ( ofcourse I know I cannot resend with Delivering Status). But not sure what causes the messages to failed with Delivering Status mode.
Any pointers would be highly appreciated.
Will increase of Parallel Queues really solve my problem? If it fails in Prod, its a big problem for us as we dont want to lose the data. Now everytime we are restarting the Message service server.
Regards,
Srinivas

Normally if there is any problem in target then you will see the adapter engine message as delivering
after the no of retires set then status will go to system error
during this entry check the CC used what is the error causing for that ?
HTH
Rajesh

Message in "delivering" status in adapter engine

Hi All,
There is a message which is in the "delivering" queue long time ago(around 1 month) and I need to know:
what is the possible cause for this issue?
how to change the status to "successfull" or "failed"?
Any help will be really appreciated.
Thanks
Ivan

Hi,
If receiver communication channel is file ftp, then check SAP note num 821267, point 45:
45. Receiver File Adapter stuck while using temporary file.
Q :The thread of receiver file adapter remains in runnable while
       Communication channel has the following configuration
       File Construction Mode=Create, Overwrite Existing File=false,           Write Mode= Use Temporary File.
A :The Receiver file adapter thread is stuck in the runnable state when the temporary file is used and over writing of existing file is set to false. Since the temporary file was not being deleted and the overwriting of existing file i.e. target file was set to false, the thread would never end. This problem has been fixed by deleting the temporary file after being named to the target file.
           The error is corrected with SAPXIAF06P patch#8 (Support              Package -level #06).
Regards,
Carme.

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

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!

To Be delivered status in Message monitoring

Hi,
There are some messages in TO BE DELIVERED status in Message monitoring while selecting integration server. I could neither cancel nor resend.
any input reg. this will be appreciated.
I didn't see any messages with TO BE delivered status in adapater engine.
I could able to clear What ever messages in system error status in adapter engine by filtering based on sequential id.
I have seen this thread & link also.
To Be Delivered
Re: "To be delivered" status in RWB -- Any solution?
http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/content.htm
I could not see any entry in SMQ1, SMQ2, SM58 also
Thanks
Praba
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:02 PM
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:04 PM

Hi,
You cannot resend or cancell the messages which are in status "To Be Delivered". Check Receiver adapter File/Jdbc/ OFTP e.t.c. which is processing these messages.
Check with your Basis team to remove the lock of adapters if any. Or to process these messages you require soft restart of Java stack.
I had same kind of issue two days back with OFTP adapter messages and did soft restart of java stack with help of Basis team.
Hope it will helps you
Cheers
Veera

BPM wait step : RWB"To Be Delivered status": SXMB_MONI"Message being sent"

Hi All,
I have a BPM interface running fine since 1 year.
In this BPM I have wait step for 5 minutes.
But yesterday message is stopped on wait and not proceeding ahead.
I checked XML is good as per mapping. and in runtime wirk bench message is still in "To Be Delivered status"
and in SXMB_MONI message column Outbound Status still showing "Message being sent" even after 12 hours.(wait is only 5 minutes). And below is the trace of last message.
Please guide how to handle or restart this message. in SMQ1 & SMQ2 there are no queues showing:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>
Regards

Solved, few BASIS jobs were inactive in transaction code "SWF_XI_CUSTOMIZING".

Messages getting stuck in Delivering status in AE

Hi all,
Recently we are coming across messages that go into Delivering status. These messages mostly belong to File Sender/Receiver Adapter but not confined to them. Here is the audit log of one such message:
2011-03-21 10:01:55 Success Write to file "/usr/sap/ZX2/EXT/XI_INTERFACES/SCP2PIF016/NOT_PROCESSED/goodsReceiptPosting_InvalidRecords20110321-100155-650.xml" as binary, size 1949 bytes
2011-03-21 10:01:55 Success File processing complete
2011-03-21 10:01:55 Success MP: Leaving module processor
2011-03-21 10:01:55 Success The message was successfully delivered to the application using connection File_http://sap.com/xi/XI/System.
2011-03-21 10:01:55 Error Setting the message status to DLNG failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..
On searching in SDN I found one work around-- to restart Messaging Service in Visual Admin. This did work as the messages got processed after that. But, the problem seems to be recurring now(once in every two days).
Can any body shed some light on this to find the permanent fix?
Thanks a lot,
Gokul.

Hi,
Make sure you have set the MaxThreadCount parameter to 350 or higher depending of the case and of the resources available.
To increase the parameter, please follow the instructions below:
1. In the left frame choose Server -> Kernel -> ApplicationThreadManager
2. In the tab Display Configuration (right frame) choose Switch between view and edit mode to activate the edit mode.
3. The parameter MaxThreadCount must be set to 350.
4. You will then need to restart the J2ee
For reference see note #937159 - XI Adapter Engine is stuck
For specific setting to an adapter can be done by going to the Visual Administrator -> Services -> SAP XI AF Messaging
Look at the property 'Messaging connections' here you will see the following queues:
Send.maxConsumers (asynchronous sending - outbound)
Recv.maxConsumers (asynchronous receipt - inbound)
Call.maxConsumers (synchronous sending - outbound)
Rqst.maxConsumers (synchronous receipt - inbound)
Depending on where the bottleneck is occurring (i.e. too many entries in the Send.maxConsumers) you can increase these parameters.
Example of parameter value syntax (sample for FILE adapter):
(name=FILE_http://sap.com/xi/XI/System, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=10, Rqst.maxConsumers=10)
For reference see note:
#791655 - Documentation of the XI Messaging System Service Properties
And see the link:
/people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
Regards,
Caio Cagnani

Messages are stuck in "delivering" status

Hi
We are doing Async RFC to JDBC Scenario. Messages are successful from R/3 to XI but getting stuck at receiver jdbc adapter . subsequent message are also stuck because of this
Below is the audit log of the message
2007-06-29 10:33:08
Success
The message status set to DLNG.
2007-06-29 10:33:08
Success
Delivering to channel: CS_CUS_PS_MAINTENANCE
2007-06-29 10:33:08
Success
MP: entering
2007-06-29 10:33:08
Success
MP: processing local module localejbs/CallSapAdapter
2007-06-29 10:33:08
Success
Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2007-06-29 10:33:08
Success
JDBC adapter receiver channel CS_CUS_PS_MAINTENANCE: processing started; party , service BUS_MES
After then it just hangs and it shows "delivering" status only
There is no error in SXMB_MONI
Any clues!!!!!!!!!!!!!!
Regards
Vijay

Vijay,
The queues in adapter are different from the queues in Integration Engine.
You can restart failed msg in adapter queues also. Stefan Grube has shown this in a weblog. Just do a search, you will get the blog.
Regards,
Jai Shankar

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 stuck in delivering status

Hi all,
I have an idoc-xi-ftp scenario with EO quality of service. For the very first tests we set up a file CC using nfs and everything worked fine.
Today I received the info to connect to the FTP server and introduce it on the file CC. The issue comes because some kind of problem writing on the ftp server leaves the messages in status "delivering" (DLNG). While FTP guys try to fix the issue (they don't know where he tissue is right now) I have switch again to NFS with the old configuration in order to allow the users to keep testing.
But the issue comes because now the messages being sent to NFS scenario are marked as to be delivered and they are not processed.
I'm suspicious about the delivering ones and I'd like to cancel, but the cancel button doesn't allow me to do it so I'm hanged in a circle.
Any ideas?
Thanks in advance,
David R.

Hi,
Yes, ABAP +Java implies a complete restart of the PI server, which is not recommended in the production environment.
Generally, this case is like a deadlock situation. We will not be able to either resend/cancel the messages in delivering.
So , best option would be to identify which server node these messages are stuck and then restart that server node.
With the server node restart these messages in Delivering are again reprocessed by the server.
Regards,
Younus

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

Trigger alert for Messages in 'To be delivered' status

Hello Experts,
We are doing proactive monitoring in our system,so we check for all messages which are in error and alert configuration is enabled which takes care of this.
But we had a critical issue where adapter queue was locked and hence,messages were in status 'To be delivered' for a long time.
There were no alerts triggered as there was no error.
The problem resolved by itself after sometime.
But such delays are not acceptable in some critical scenarios.
Can anyone please help us and let us know know how can we trigger alerts in such cases,say,if a message is in status 'To be delivered' for more than 30 minutes ,an alert should be raised.
Also,in RWB Message Monitoring Audit log,I can see message start time as 12:25 and end time as 13:57,i.e. a difference of 1 hr 32 minutes.
Is this data stored in some table in ABAP stack,so that I can take this data and create an ABAP report to trigger a mail if this threshold is reached?
Kindly help.
Regards,
Shweta

But we had a critical issue where adapter queue was locked and hence,messages were in status 'To be delivered' for a
long time.
There were no alerts triggered as there was no error.
We have to do the monitoring manually. Alerts wont be raised in such cases.
Is this data stored in some table in ABAP stack,so that I can take this data and create an ABAP report to trigger a mail if this
threshold is reached?
Data in the table SXMSPMAST may help.
Regards,
Abhishek.

Urgent - Messages in "To Be delivered" status

Hi XI ers,
We have around 150 messages in "To Be delivered" status. Tried resending a couple of them but no sucess.
When tried to resend a message, it gives message 2 Audit log entries in MDT (Message Display Tool). The first entry is "Try to fail the message" and "Trying to resend the message"
After that in RWB, message monitoring, the status of the message is "To Be delivered" forever.
>>there are no queue entries (smq1 and smq2)
>> tried cancelling the first message in the list of "To Be delivered" status.. and that did not work.
The error being in Receiver end, there are no error entries in sxmb_moni also.
Can any help me with what the issue could.
Any suggestions on directing me are welcome,
thanks,

hey
have a look at the followin
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
thanx
ahmad

Message in Delivering status

Similar Messages

Maybe you are looking for