Adapter Engine - "To Be Delivered"

Hi Guys,
I was hoping someone might be able to help. We have allot of messages in out Adapter engine which is stuck in to be delivered. Nothing is failing and the comm channel monitor is fine. Seems like the messages are just processing very slowly. It's been queuing up for a week now and stands at 7000 messages. On R/3, SMQ2 the messages also times out. We tried to restart the system also the java engine with doesn't seem to help.
Any ideas what I can do?
Thanks,
Jan

let me explain ,
Every adapter had predefined open connections by defulat 5 to handle parllel requests,if your interface is going handle more messages at one shot then def it will take some more time deliver messages to target system.
even you can check the how many number of conection is using whil checking
Copeonent monitporing-->adapyter engine->engine status.
some times you have to invreate the value to required number.
refer below blog
/people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements
Regards,
Raj

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

  • JBBD Sender - Problem with Adapter Engine - Message status Delivering -

    Hi all,
    I've a rare problem. My scenario is JDBC (EO) to IDOC. If the SELECT query from SQL database arrows 8000 lines, the message was sent from PI to R/3 succesfully and Idocs was generated.
    But if the query is larger than 10.000 lines, the message was stopped in the sender queue in AE with status "Delivering". In SXMB_MONI I can't see the message, only in RW in Message Monitoring or Component Monitoring in Engine Status.
    I've applied note  Note 937159 - XI Adapter Engine is stuck, and follow this blog
    /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
    Using Configtool I modified these parameters (MaxConsumers). But message still puts in sender queue.
    I have in PI 7.1 SPs 0004.
    Any suggestions??
    Edited by: Pablete on Sep 13, 2010 8:41 PM

    I have the same requirement and for solving this, I have to apply a very complex select statement.
    But it works perfekt for MS SQL:
    select * from table where order_no in (SELECT distinct top(1000) order_no FROM table where any_clause) and any_clause order by order_no
    update table where invoice_no in (SELECT distinct top(1000) invoice_no FROM table where any_clause) and any_clause
    I create an IDoc for each order_no, so I have to make sure, that all lines belonging to one invoice are in the same select.
    My select statement has 463 characters

  • 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

  • Messages got stuck in Adapter engine

    We are doing http to RFC sysnchronous scenario
    Message got stuck in adapter engine.so we are getting 500 HTTP timeout error in Http client.
    Please help us to find why messages got stuck in Adapter engine.
    Below Adapter engine audit log message is pasted for your reference.
    Audit Log message:
    Time Stamp Status Description
    26.09.2008 06:33:54 Success Message successfully received by messaging system. Profile: XI URL: http://devsap01:51000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    26.09.2008 06:33:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
    26.09.2008 06:33:54 Success Message successfully put into the queue.
    26.09.2008 06:33:54 Success The message was successfully retrieved from the request queue.
    26.09.2008 06:33:54 Success The message status set to DLNG.
    26.09.2008 06:33:54 Success Delivering to channel: RFC_out_Test
    26.09.2008 06:33:54 Success MP: entering
    26.09.2008 06:33:54 Success MP: processing local module localejbs/RfcAFBean
    26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for ZFTestRFC
    26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for J2EE_GUEST
    ime Stamp Status Description
    26.09.2008 06:56:15 Success MP: leaving
    26.09.2008 06:56:15 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Setting message to status failed.
    26.09.2008 06:56:15 Error The message status set to FAIL.
    26.09.2008 06:56:15 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired..
    Kindly advise us on this issue.

    Hi krish,
           when i send a http request it got stuck in adapter engine with status "delivering" for some time....
    We found that RFC got successfully executed in R/3 system but the synchronous message is not delivered to PI.since adapter engine message is having status "delivering"
    after some time we got adapter engine message status as "cancelled with error"
    Error is Message expired exception which you can see audit log message I have pasted in my previous post.
    Meanwhile we also got HTTP timeout error in Http client.
    Could you please tell me why it got stuck in Adapter engine with status "delivering" since RFC is executed successfully.
    Why we are not getting synchronous message reply back to PI?

  • 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

  • How to see old successfully delivered messages in Adapter Engine

    We are unable to see the messages that were successfully delivered  by Adapter Engine more than a day.Ho do we see old successfully delivered messages by Adapter Engine.We are only able to see the messages that were 1 day old.We are using PI 7.1.
    We are able to see the older messages in Integration Engine as per the config  in sxmb_adm.
    Any Help greatly appreciated.
    Thanks,
    Aravind

    Only message that contain error,holding,not delivered are getting persisted not the sucessfully delivered ones.
    Is there any Archiving scheduled for your Adapter Engine?
    I want to see the old messages that were delivered sucessfully
    In Message Monitoring Itself select Archive (instaed of Database) and make a search.....if archiving is scheduled then you should be able to see the messages by this option.
    Regards,
    Abhishek.

  • How to delete / cancel messages in PI adapter engine

    Hello expert,
    we have a scenario File (EOIO) --> PI --> ABAP. Today the file we received is big (>100mb), apparently PI can't handle it, and we got error
    Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException:
    Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.
    seems like PI adapter engine got problem while delivering the huge message to ABAP integration engine. In RWB message monitoring, the message is set to Error. Unfortunately the file has been picked up many times, thus the huge message is stuck in adpater engine. In RWB message monitoring, I can see the message listed many times and status is HOLDING because the previous message can not be delivered to Intergration engine. I want to delete/cancel all the messages, I tried in RWB message monitoring to cancell the messages, however after cancelling one message, it crashed the PI system and cause a reboot.
    My question is; Is there some place in NWA (net weaver admin) to force all the messages to be deleted? (Because deleting/cancel in RWB message monitoring does not work because it causes system crash).
    Thanks
    Jayson

    Hi Team,
    I couldn't able to delete old message's from one of Q system, Persistence layer is 584 % filled, after triggering delete job(RSXMB_DELETE_MESSAGES) and Persistence layer has come to 384% and further I couldn't able to delete old messages.I executed program "
                                                                                                          RSXMB_CHECK_MSG_QUEUE" and manage  to delete few entries.Could you please suggest how to reduce fill level to below 100%
    Switch Procedure (for Persistence Tables) Deactivated
    Number of Table Entries                                                           
    3.185.992
    Maximum Number of Table Entries                                                   
    830.000
    Current Fill Level in %                                                           
    384
    Threshold value for fill level for executing a switch run in %                    
    60
    Number of Logically Deleted Table Entries                                         
    0
    Decline of Fill Level in % Following Deletion                                     
    384
    Delete or archive processed XML messages
    Job log overview for job:    SAP_BC_XMB_DELETE_001 / 06302000
    Date       Time     Message text                                                                               Message class Message no. Message
    13.03.2013 06:39:55 Job started                                                                                     00           516          S
    13.03.2013 06:39:55 Step 001 started (program RSXMB_DELETE_MESSAGES, variant &0000000000034, user ID SAPBATCH)      00           550          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ASYNC: 1                                        XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ROWS: 100                                       XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-IDX5_DELAYED: 0                                 XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-ROWS_PER_LOOP-DELETE: 100                                       XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-ASYNC: 007                                     XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-SYNC: 007                                      XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR-SYNC: 007                                XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-IDX5: 007                                      XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-ASYNC: D                                  XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-SYNC: D                                   XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR_UNIT-SYNC: D                             XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-IDX5: D                                   XMS_ADM        375          S
    13.03.2013 07:27:58 0 XML messages deleted                                                                        XMS_ADM        351          I
    13.03.2013 07:27:59 Step 002 started (program RSXMB_TABLE_SWITCH, variant &0000000000034, user ID SAPBATCH)         00           550          S
    13.03.2013 07:28:00 Job finished                                                                                    00           517          S

  • Shutdown of XI 3.0 Plain J2SE Adapter Engine.

    How do I shutdown the XI 3.0 Plain J2SE Adapter Engine? Where should I go to do this?
    Regards,
    N.S

    Hi N.S. -
    If I recall correctly, you open a browser to http://<host>:8200 .   8200 is the default port.  If not using the default port, you may need to investigate what that port is.  Delivered initial user/pwd is sap/init.
    There's a Shutdown Adapter Engine option once you get in.  Of course, the j2se adapter engine must be running in order for you to do this.
    Regards,
    Jin

  • Receiver File Adapter J2SE Adapter Engine

    Hi,
    We have configured a receiver file adapter on a J2SE adapter engine through the administrator page of the J2SE adapter.
    XI.httpPort=8222
    XI.httpService=/file/Receive
    and the rest of the adapter parameters.
    I have configured a channel in ID as XI receiver adapter.
    host: "hostname"
    Service: 8222
    Path Prefix: /file/Receive
    The messages in sxmb_moni fail to be delivered with "HTTP error 404 Resource not found."
    Through a browser I am also not able to make a connection to this url:
    "host":8222/file/Receive
    Getting Http error "501".
    Please can someone shed some light on this problem.
    Regards
    Willie Hugo

    >Through a browser I am also not able to make a connection to this url:
    >"host":8222/file/Receive
    >Getting Http error "501".
    This is ok. Since get method not implemeted for this service.
    Since from XI you are getting this error "HTTP error 404 Resource not found", can you logon to XI server at OS level and do a telnet test to check if the port is working.
    cmd> telnet
    telnet> open <J2SEAdpaterEngineHostName (or) IPAddress> 8222

  • Delay of Message in the Adapter Engine when put into queue

    Hi XI/PI Experts,
    We are having problems in the Adapter Engine wherein messages are staying longer in the AE queue as usual.  Sometimes, it stays longer in Delivering status also.  Is there any way we can monitor and try to push the message out of AE to avoid delays?  I know we can do this in the ABAP side (Integration Engine)...but how can we do this in the Adapter Engine?
    See below sample logs in AE RWB:
    2008-07-17 13:28:13 Success Using connection SOAP*****. Trying to put the message into the receive queue.
    2008-07-17 13:28:13 Success Message successfully put into the queue.
    2008-07-17 13:34:12 Success The message was successfully retrieved from the receive queue.
    2008-07-17 13:34:12 Success The message status set to DLNG.
    As you can see there is a gap of 4 minutes.
    Hope you can help me.  Thank you so much in advance.
    Grace

    Hi.
    Thanks for your answers but the messages are not set into EOIO but just EO.  So the messages are not ending up in Holding Status. 
    I also believe that issue is not occurring because of too many messages in error in AE nor because of the receiving system is down.  Issue is happening when message is about to be sent to the SOAP communication channel in AE.  As you can see in the sample log I provided above, in RWB AE, after the message was put into queue, it took several minutes to be delivered to corresponding comm channel.  My questions are:
    1.  Is there a way we can monitor the queue in AE like the way we monitor the queue in IE? (e.g. smq1 and smq2 transactions) .
    2.  If there is a way, how are we going to intervene manually on the queues in AE?  (we can intervene with smq1 and smq2 in IE)
    3.  For messages with Delivering Status in AE, sometimes it is taking hours to move to "Successful/Delivered" Status.  Is there a way we can intervene with that?  I believe we can resend messages with "System Error" Status and Staus "To be Delivered" but for status "Delivering"...it is not possible (from what I know -- I hope there is a way).
    I look forward to hearing from you guys/gals.
    Grace

  • Messages got stuck in inbound adapter engine queue

    Hi Experts,
    My senario is File - XI -SAOP reciever and we have 8 usecases of same type. For 7 usecase, we dont have any problem. But for only one use case we have having heavy delay in processing messages.
    All  my messages got stuck in inbound queue of Adapter engine in to be delivered state, wait state, delivering state.
    Please see the below logs and suggest some solution.
    To be delivered Message log  :
    Time Stamp Status Description
    2008-06-30 06:54:20 Success Processing child message of multi-message with message ID 8c597510-466f-11dd-92f9-000f203c93e0
    2008-06-30 06:54:20 Success Using connection AFW. Trying to put the message into the receive queue.
    2008-06-30 06:54:20 Success Message successfully put into the queue.
    Waiting Message log :
    Audit Log for Message: 4864ad2b-cabd-5891-e100-00000aa3fdb2
    Time Stamp Status Description
    2008-06-30 06:42:24 Success Processing child message of multi-message with message I
    2008-06-30 06:42:24 Success Using connection AFW. Trying to put the message into the receive queue.
    2008-06-30 06:42:24 Success Message successfully put into the queue.
    2008-06-30 07:46:16 Success The message was successfully retrieved from the receive queue.
    2008-06-30 07:46:16 Success The message status set to DLNG.
    2008-06-30 07:46:16 Success Delivering to channel: CC_SOAP_Receiver
    2008-06-30 07:46:16 Success SOAP: request message entering the adapter
    2008-06-30 07:51:24 Success SOAP: call failed
    2008-06-30 07:51:24 Success SOAP: sending a delivery error ack ...
    2008-06-30 07:51:24 Success SOAP: sent a delivery error ack 
    2008-06-30 07:51:24 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2008-06-30 07:51:24 Error Exception caught by adapter framework: Read timed out
    2008-06-30 07:51:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2008-06-30 07:51:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Jun 30 07:56:24 GMT 2008.
    2008-06-30 07:51:24 Success The message status set to WAIT.
    Delivering Message log :
    Audit Log for Message: 4864ad2d-cabd-5891-e100-00000aa3fdb2
    Time Stamp Status Description
    2008-06-30 06:42:24 Success Processing child message of multi-message with message ID 7481f110-466f-11dd-b8ce-000f203c93e0
    2008-06-30 06:42:24 Success Using connection AFW. Trying to put the message into the receive queue.
    2008-06-30 06:42:24 Success Message successfully put into the queue.
    2008-06-30 07:46:24 Success The message was successfully retrieved from the receive queue.
    2008-06-30 07:46:24 Success The message status set to DLNG.
    2008-06-30 07:46:24 Success Delivering to channel: CC_SOAP_Receiver
    2008-06-30 07:46:24 Success SOAP: request message entering the adapter
    2008-06-30 07:51:24 Success SOAP: call failed
    2008-06-30 07:51:24 Success SOAP: sending a delivery error ack ...
    2008-06-30 07:51:24 Success SOAP: sent a delivery error ack 
    2008-06-30 07:51:24 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2008-06-30 07:51:24 Error Exception caught by adapter framework: Read timed out
    2008-06-30 07:51:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2008-06-30 07:51:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Jun 30 07:56:24 GMT 2008.
    2008-06-30 07:51:24 Success The message status set to WAIT.
    Thank you
    Subbu

    Dear Subramanyam,
    Some message might be struck in the queue. Because of this reason furthur processing is not performed on time.
    Please try to do like this:
    Go to SXMB_MONI, or SXi_monitor, select QueueID in the row, which is showing green flag. In the next window belongs to queue select the queue and press unlock button on the panel.
    This could possibly release the queue which is struck.
    Best Regards
    Praveen

  • Messages goes into scheduled status in adapter engine

    Hi all
    we are doing idoc to file scenario with direct mapping. the messages are getting processed in integration engine sucessfully. the messages are getting into scheduled status in the adapter engine even when there is less load in the server.
    Thiis specially happening for IDOC to file scenario only.  Any help is highly appreciated
    Thanks

    >
    > the system is quite good at the moment but the some of the messages again into scheduled status like ( 10 out of 1000 messages ) . the system is not performing at 100 % rate since some messages moves to scheduled status.  Is still the performance can be improved in any other ways ?
    >
    This is really strange behaviour , If Communictaion channel functioning correctly then all succesfull messages should deliver to Receiver system.
    Better to check payload of scheduled messages(if wrong payload obiously it goes schedule status),try to to reprocess them.
    I never used XCOPY command,so no comment on that.
    Regards,
    Raj

  • Message Archiving for the Adapter Engine

    Hi,
    we have configured archiving for Integration Engine (SXMB_MONI) messages on the Production XI System. is it necessary to configure Message Archiving for the Adapter Engine also ? in which scenarios archived adapter messages are useful ? are there any other advantages/disadvantages for this(in case of errored messages on the adapter engine) ? Please share any ideas.
    Thanks
    Pavan.

    >>is it necessary to configure Message Archiving for the Adapter Engine also
    Not necessary,but depends upon the scenario,lets say you are posting messages to external partner's FTP and there was some issue in connectivity due to which file was not delivered,in this case you need to send the message again.
    same thing can happen in inbound messages too.
    >>in which scenarios archived adapter messages are useful ?
    i would do this specifically for JDBC sender coz once you pick up the files based upon SQL query,you change the flag so that those values are not picked next time,in this case you can't re-run the old query and get same results.
    this also holds for proxies and file too.
    Thanx
    Aamir

  • Missing Audit Log of Adapter Engine in Message Monitoring

    Hi!
    I've a problem with a fresh installed PI:
    The Adapter Engine doesn't log anything in the Message Monitoring. The Integration Engine logs everything properly, but all entries from the adapter engine are missing. It looks like no message was processed by the AE, but in fact AE is processing the messages properly, only logging fails.
    What can cause this behaviour?
    Best regards,
    Daniel

    Hi Agasthuri,
    yes, maybe something gone wrong in the post install, I will ask the guy which did the installation of the PI. Therefore I didn't have the logon data for performing a cache refresh, but in the log entries it seems that this is working properly.
    Hi Praveen,
    in Communication Channel Monitoring (In PI this is no longer found under Adapter Monitoring), I can see that the messages are delivered, but I can't see the Audit Log entries there.
    I checked the MDT, but there are also no messages displayed.
    End-to-End-Monitoring seems to be a good solution, but it seems that it is something configured wrong in this installation I will try to get the guy which cares for Basis to look after it.
    Best regards,
    Daniel

Maybe you are looking for