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

Similar Messages

  • 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

  • Adapter engine in red color status

    Dear All,
           I got pi production system.When i verified componenet in RWB everything is fine except adapter engine.
    Adapter Engine in red color status.Error in Are registrations of connections and protocol handler without errors?
    I clicked on details.Please see below
    13 of 23 connection(s) registered successfully(it was showing 5 of 23 success after i restarted it's showing 13 of 23)
    8 of 8 protocol handler registered successfully
    Connection registration failed for connection BC_http://sap.com/xi/XI/System on node 106310950 due to: Failed to register connection BC_http://sap.com/xi/XI/System. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue BC_http://sap.com/xi/XI/SystemRecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection.
    Possible reasons:
    1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks.
    2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable
    3) Connections are not enough for current load.
    I tried many ways to resolve this problem unfirtunately i couldn't.Whether this gives any issues i mean shall i ignore this if not please suggest me to resolve this.
    Thanks in advance
    Regards
    Kumar

    Dear Team,
    I am facing the same issue in SLD(PI Java Stack).
    Please find below snapshot. Please Help. Many Thanks .....

  • Cannot see adapter engine messages in message monitoring

    hi guys,
    i cannot see my adapter engine messages in message monitoring for my http to RFC syncronous scnenario.
    i can however see the integration engine messages and can also see the receiver RFC channel in  communication channel monitoring

    Hi
    this link ll help u in it -
    Adapter Engine monitoring is provided in detail. Try as mentioned
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/7c/14b5765255e345a9e3f044f1e9bbbf/frameset.htm
    Regards

  • Adapter Engine Message Archiving

    Hello,
    Can anybody share with me the guide for Adapter Engine Message archiving for PI 7.1
    Thanks ,
    Loveena

    Hi,
    Refer these links, it should help
    XML Data Archiving - Configuration Guide for J2EE Applications
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/65901c2e-0801-0010-e79a-de4ed9275d70?quicklink=index&overridelayout=true
    http://help.sap.com/saphelp_nw04/helpdata/EN/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
    Re: Archiving message PI7.1 Could not find msg in archive error
    Regards,
    Nithiyanandam

  • Authorizatoin error while viewing adapter engine messages

    I got below error from user and need to resolve.
    When I try and view adapter engine messages in XI Development system, I get the message "noAuthorizationJava"

    hi
    see this
    http://www.erpgenie.com/sap/netweaver/xi/xiauthorizations.htm
    also sap note 768456 - 928862
    Thanks
    Rod
    Edited by: Rodrigo Pertierra on Mar 27, 2008 11:24 AM

  • 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

  • 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

  • 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

  • Adapter engine messaging URL returns HTTP 403

    Hi all,
    I currently have a problem with the following scenario: SOAP Adapter -> XI -> JDBC Adapter. I have configured the scenario and everything seems to be running correctly (in the component monitoring the adapters and the integration engine are green). However when I send a request to the SOAP Adapter I get the following response:
    <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context>XIAdapter</context>
                             <code>DeliveryException</code>
                             <text><![CDATA[
    com.sap.aii.af.mp.module.ModuleException
         at
    Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 403.
    </text>
    </s:SystemError>
    In the Message Display tool of the runtime workbench I get the following trace:
    2005-06-05 11:03:08 Success SOAP: request message leaving the adapter (call)
    2005-06-05 11:03:08 Success Application attempting to send an XI message synchronously using connection AFW.
    2005-06-05 11:03:08 Success Trying to put the message into the call queue.
    2005-06-05 11:03:08 Success The message was successfully retrieved from the call queue.
    2005-06-05 11:03:08 Success The message status set to DLNG.
    2005-06-05 11:03:08 Success Message successfully put into the queue.
    2005-06-05 11:03:08 Error Returning synchronous error notification to calling application: Received HTTP response code 403..
    2005-06-05 11:03:08 Error Transmitting the message using connection http://<host>:8000/sap/xi/engine?type=entry failed, due to: Received HTTP response code 403..
    2005-06-05 11:03:08 Error The message status set to FAIL.
    2005-06-05 11:03:08 Error Returning to application. Exception: Received HTTP response code 403.
    So it seem that somehow the adapter framework is not allowed to send a message to the integration engine via the messaging URL.
    Any ideas how to resolve this problem?
    Thanks for you help,
    Christian

    Hi,
    If you've changed the passwords for XI service users
    then you may also want to check this note: 721548
    XI 3.0: Changing the passwords of the XI service users
    Regards,
    michal

  • How to archiving Adapter-Engine messages in PI 7.1

    Hello,
    How do I archive messages in Adapter Engine side in PI 7.1.
    Does anybody know some document describing that ?
    Arthur Silva

    Hi ,
    please go through the below link.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0afdd69-a8a7-2d10-7e9a-cbf6fa21c5a7?QuickLink=index&overridelayout=true&49061411503734   ---  STEP BY STEP
    http://scn.sap.com/thread/1498569
    http://wiki.scn.sap.com/wiki/pages/viewpage.action?original_fqdn=wiki.sdn.sap.com&pageId=147266890
    Regards
    srinivas

  • RWB-Mesg Monitoring-Adapter Engine-Message Retention is only 1or2 days

    Hello Experts,
    I have a an Integrated Scenario, SOAP to RFC, in my landscape. As you know I can only monitor messages for an Integrated Scenario in Runtime Workbench -> Message Monitoring -> Adapter Engine. So, when I find my message related to the Integrated Scenario and click on "Message Details" I am not able to view the payload for any of these messages. I am sure there is somewhere on the Java stack flip the switch to view payload but not sure where. Any kind of help would be greatly appreciated.
    Thank you!!

    Please follow steps as below...
    1. Open http://server.domain.ext:5XX00/dir/start/index.jsp (Please modify according to your server name, domain URL and Port)
    2. Navigate and open Runtime Workbench after you log on
    3. Navigate and open Message Monitoring 
    4. Select appropriate Messages from Component: and From
    5. You will able to see Refresh button then |  View: and Time:
    5. Drop down Time: and you will able to do selection there Hourly, Daily, Weekly, Monthly and Yearly...
    Please let me know if you have any other question.
    Regards,
    Yogesh Patel

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

  • Adapter Engine - Messages in To Be Delivered status

    Hello,
    I am using a SAP XI 3.0.
    Checking the Message Monitoring, I have seen that there are a lot of messages in status To Be Delivered. I think that this status in an initial status because then the message has to be set to Delivering in a next step.
    Specifically, the mentioned status is related to a Communication Channel which is configured as below:
    Adapter Type: XI
    Transport Protocol: HTTP 1.0
    Addresing Type: URL Address
    Target Host: A determined value
    Service Number: A determined value
    Authentication Type: Use Logon Data
    User Name: A determined value
    Password: A determined value
    There is no module added in Module tab.
    I think the problem is that messages are queued requesting any information but I do not know if there is any place to check it (in smq2 transaction, the queues are empty and this kind of channel is not shown in Communication Channel Monitoring).
    Thanks in advance.
    Best regards,
    Gemma
    Edited by: Gemma Boldu Capdevila on Oct 21, 2009 3:08 PM

    Hi,
    You have to clear that particular queue in message monitoring of RWB.
    Check the following links:
    http://help.sap.com/saphelp_nw70/helpdata/en/45/d4b62755002e97e10000000a155369/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/49/e3fb40ef74f823e10000000a155106/content.htm
    Your problem should be solved now.
    Regards,
    Supriya.

  • Archiving Adapter Engine Messages

    For AE we have implemented the Archiving:
    The steps for AE we took are as follows:
    1. Created archive store, and after that done home path synch and assigned it to an archive path.
    2. created the archiving  background job in RWB with rules and have default delete job in place.
    Archiving job is running once in a day. But Default persistance duration of messages in AE is 30days.
    Here I have some confusions in understanding the core logic.
    1. Whether messages which have completed their 30 days of life will be archived ?
    2. or messages which have completed 1 day of life will be archived(Since archive job runs every day) ?
    3. I have seen Archive and delete jobs have different run times, even though delete job didn't completed yet, archive job
    is deleting the messages from database. Why it is happending like that ?
    4. Does we need both the archive and delete jobs or archive job alone is fine ?
    Thanks
    kumar

    Kumar,
    Here are my thoughts.
    1. Whether messages which have completed their 30 days of life will be archived ? - NO
    2. or messages which have completed 1 day of life will be archived(Since archive job runs every day) ? - YES
    3. I have seen Archive and delete jobs have different run times, even though delete job didn't completed yet, archive job
    is deleting the messages from database. Why it is happending like that ? -
    Archive jobs will archive the files to the directory mentioned. you might not have access to the archive directories. i don't think the files will be deleted if you have specified Archive parameter.
    4. Does we need both the archive and delete jobs or archive job alone is fine ?
    Archive jobs alone is fine, if you have a specific directory to hold archive msgs.

Maybe you are looking for