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

Similar Messages

  • 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?

  • How to remove large message stuck in the adapter engine?

    Hi experts,
    We have a large message abt 100 MB stuck in the adapter engine which is causing the J2EE server to restart continuously.
    I have tried increasing the heap sizes and the number of threads in config tool, but no luck. My question here is how to remove that message? Also I checked smq1 and smq2 both are empty.
    Regards.

    Hi Nagasatya,
    This issue is realted to Large amount of data.You have to write condition in the query.I have face same issue,but resolved it.Please do the following steps.
    Go to Configtool and selct the com.sap.aii.adapter.jdbc.svc and set this jdbc service to start manually instead of auto.
    Then restart server0, this time it should be started successfully. Then go to rwb and try to
    find if any jdbc hanging/failed messages are there, if so, cancel them;also deactivate the problematic jdbc communication channel, otherwise itwill poll the data again. After all above, you can manually try to start this jdbc.svc particually.
    Thanks
    Ravi

  • Adapter Engine Queue

    Hi.
    I got yhe following error in default trace.
    ==========
    Could not get next EOIO QueueMessage from MessageStore. Reason: com.sap.aii.af.ra.ms.api.MessagingException: Error retrieving message from database store. Reason: Could not create Message. Reason: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Binary index out of range: 1613824 Putting message back into sequencer for manual retry.#
    #1.5
    ==========
    I check the
    http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp, and found the following information.
    ?EOIO   Status   HOLD  -> 1
    ?????????   TBDL  -> 1
    ?Matrix  one of the Adapter
    ???????????TBDL -> 6
    ???????????Size -> 161384
    I think the Adapter Engine queue size is overflow.
    (It is 161384).
    Question1
    How can I restart this "TBDL" message?
    I tried to restart from RWB -> message monitoring,
    but could not deliver cause of error.
    Question2
    How can I change the "queue size"?
    There are documents that refer to "thread count",
    not but "queue size".
    The thread count is default. It's "5".
    best regards,

    Thank you for your replying.
    I retry the message, but the error occured again.
    I check this message by performance monitoring on RWB.
    Nomarry this inerface process the "5 messsages" at one time.
    The average message size is "2MB".
    The "TBDL" message size is 2MB(I mean average size),
    but the number of the message is "19"!!
    Should I increase the number of threads?
    regards,

  • Deleting Adapter engine queues

    Hi Experts,
                     While trying a proxy to database scenario My message is (processed Successfully in SXMB_MONI) getting stuck in Receiver JDBC channel and the status of the message is DELEIVERING. How can i delete the messages from the adapter engine queue. I am trying to cancel the messages from the Message monitoring in the RWB but i am not able to cancel that message due to which other messages are also in DELEIVERING state.
    Thanks
    Ajay

    Hi,
    1) How can i know the Queue ID in the Adapter engine as my message is processed succesfully from SAP-XI and stuck in adapter engine.
    A) See the Blog for this
    2) Is it mandatory that we have to clear the Very First message which is in the queue , means other messages which all are in DELIEVERING stage can't be deleted?
    A) YES, Its mandatory to clear the very first strucked message
    Regards
    Seshagiri

  • Adapter engine queue monitoring

    Hi All,
    I have one doubt about adapter engine queue.
    We can see adapter engine queue in  RWB->Message Monitoring-> Adapter engine-> Display  .
    Here in queue if one message goes in to system error status, remaining all messages from that queue goes on holding status.
    So unless someone manually clears this system error message, remaining messages from same queue will not be processed.
    Is there anything to automate this process? Because currently someone has to manually monitor this queue and clear the message if it is in system error.
    Thanks in advance.
    Warm Regards,
    Gouri

    Hi Bhavesh,
    I am getting a PO file from source system which contains data and control record. But target system expects two different files for data and control. So in mapping program I have done this.
    When interface split happens for one scenario and the multiple messages are going to the same receiver, an internal queue name is generated from the message ID of the original message, to ensure that the correct processing sequence is maintained. As a result, the quality of service switches from EO to EOIO. Here is the reference link:
    http://help.sap.com/saphelp_nw04/helpdata/en/28/68073c8e56f658e10000000a114084/frameset.htm
    Also can you please elaborate on CCMS?
    Thanks in advance.
    Warm Regards,
    Gouri

  • Getting message Attempt to determine which Adapter Engines......

    Hello All
    1. I am Getting System message 'Attempt to determine which Adapter Engines are affected by data changes failed' in the Integration Directory.
    Updating SOAP Adapter (Sender channel).
    Refreshed all caches...
    2. Also while testing using SOAP Test client getting response
    HTTP/1.1 500 Internal Server Error
    connection: close
    set-cookie: JSESSIONID=(XIServerName_03)ID1387309050DB21025913116517472411End; Version=1; Path=/
    set-cookie: saplb_*=(XIServerName_03)31556950; Version=1; Path=/
    server: SAP J2EE Engine/6.40
    content-type: text/xml; charset=utf-8
    any idea?
    Thanks in advance

    Hi Naveen
    Thanks for your reply...
    Actaully previously sender channel was working fine, i just updated the default namespace in the channel.
    I was getting the error because of wrong namespace in channel (Case sensitive).
    So i updated this name space and after activation i am getting above message while testing.
    Regards

  • Message do not exists in adapter engine

    I have a message being sent to IE via JMS Adapter . In Communication channel monitoring i could see the message Id & error message(Error in converting Binary message)  but with that message id i could not find any entry in Message monitoring - > Adatpter Engine.  Moreover , In communication channel monitoring the id with which the message failed is not hyperlinked to "Message Display Tool (Detail Display) ".
    I need the message which is failed.
    Thanks ,
    Satish

    It may be possible that message came into error as soon as it was picked by the sender channel. Could you see some error for these messages in Communication channel monitoring? Another possibility is your message is persisted in the adapter engine for very short duration. In that case, if it is archived, you may select the Archive option in Message Monitoring instead of Database option.
    Regards,
    Prateek

  • In my Component monitoring i got this error for Adapter engine status.

    In my Component monitoring i got this error for Adapter engine status. Status is in red..
    Attempt to fetch cache data from Integration Directory failed; cache could not be updated
    [Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.03.server3, string], target element type: SAP_BusinessSystem)
    Please clarify ASAP..
    Thanks..

    HI,
    See below links you will get ..
    Process Integration (PI) & SOA Middleware
    ERR:Could not find SLD name for XI Application "DIRECTORY"
    Unable to find an associated SLD element
    Regards
    Chilla..

  • Message Got Stuck in Adapter Engine

    Hi All,
    Currently i am facing one problem with Adapter engine. The issue is we have one FILE to RFC to FILE scenario. Source file got picked at 7:15 AM in the morning. But XI placed the target file at 8:05AM. so XI it took 50 mintues to process the file. But in SXBM_MONI the time difference between request and response messsages in 6 seconds.
    Where as as per the logs in RWB, Adapter engine too 50 minutes to process a single fine.
    Here my question is waht could be the reason for this delay in processing and waht should i do to avoid such delays in real time.
    Please help me out in this. Thanks in adavance.
    Regards,
    Manjula P.

    Hi,
    The link for message diaplay tool
    http://server url:Port/MessagingSystem/monitor/monitor.jsp
    Click on Sent messages=>Synchronous. Give the proper time when error was occured. The second column is audit log and send the details to us thru the same thread.
    and
    Click on recevied messages=>ASynchronous. Give the proper time when error was occured. The second column is audit log and send the details to us thru the same thread.
    Thanks,
    Ramesh

  • Message stuck in Adapter Engine queue with status "Delivering"

    Hi All,
    I have a File to File EOIO scenario. The messages are sucessfully delivered from IE to AE. All entries have a chequered flag in SXMB_MONI. No messages are stuck in IE queue (SMQ2). But the message is stuck in AE queue with status "Delivering". I can not resend or cancel the message coz the status is "delivering".
    The reason it is in "delivering" status is due to some config error that I made in Communication Channel FTP parameters. Now it is corrected. But how do I deal with this message now?
    Restart of server is not an option here. Is there are place I can delete the message from AE queue?
    Thanks
    Jaishankar

    You can see the queues status (and number of stuck entries etc) through the link:
    http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp
    There, you can maintain the queues.
    There is also a link for the EOIO Sequence Monitor:
    http://<host>:<port>/MessagingSystem/monitor/sequenceMonitor.jsp
    There you can see the stuck messages and maintain these.
    Make sure to handle the proper message IDs.
    All of these are acessible through the Messaging System main page:
    http://<host>:<port>/MessagingSystem/
    Regards,
    Henrique.

  • Messages getting scheduled in SAP ECC Box:Messages getting stuck in Inbound

    The scenario is -
    JDBC Sender-->> SAP PI-->> ECC Server(via ABAP proxy)
    The Interface is running properly in SAP PI & then the messages are getting posted to the Inbound queues in SAP ECC Box. Generally it takes few seconds for the messages to get processed, but now all are getting scheduled in the Inbound queues(in different channels as seen in SMQ2)
    We re-ran the interfaces again a few times, but all of them kept getting scheduled. Finally, after 2 hours one of the messages got processed. I suppose we won't face any problem now onwards.
    Though I can see several suggestions like registering the queues & assigning dedicated queues to the interface, none of the blog suggest the probable cause of the event?
    Can this be due to some issue in the server(heavy pressure of data in the server during the period/issue in the queues??)
    I found the following links regarding issues like these --
    XML file getting stucked in queue in ECC
    Message in scheduled state
    Thanks

    Is the printing issue with one specific printer or across system.
    What method you have configured for output device.
    There should be any issue if you add spool work process to Application server.
    Then you should be able to configure spool server load balancing. (Search on help.sap.com for spool load balancing)

  • 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

  • Error resending messages with system-error in Adapter Engine

    Hi all,
    We got an error when trying to resend all messages in error in runtime workbench, message monitoring, adapter engine, database (overview), clicking on a sender service with messages in error state, and clicking on "repeat" button to resend those in error messages. The error is "No authorization to execute action for component Adapter Engine XP0". The user We are using to perform this task is associated to all groups available in CUA... some of you has any tips about how to perform this operation?
    regards.
    roberti

    I really don't remember what solved this problem, but it is solved. Now the functionality works as it should.
    Regards.
    Waldemar Roberti

  • Messages in "holding "status in Adapter engine

    Hi All
    We have a problem with the messages being stuck in " Holding " status
    We have resent the payloads for these messages,
    Although these messages have been manually processed,
    1) Messages went into holding status and are still remaining with the same status
    2) What we need to do to get rid of message ie. cancel, delete etc.
    Please dont send links, A solution will be appreciated
    Kindly help

    Rajeev
    I followed  this
    /people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
    and the messages did get cleared
    However on the date it got  stuck to the Holding state
    it is still showing so .
    and am unable to get rid of  the same status for these messages for that date .. even tried a cache refresh but doesnt help
    kindly suggest
    /people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework

Maybe you are looking for