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.

Similar Messages

Message stuck in adapter engine with status Hold, how to delete those

Hi,
In Dev system around 6 lac messages are stuck in ;holding' state. How can I delete them. Is there is any standard proge which can delete all these messages.
Can I delete messages of IE with status 'recorded'?
Regards,
Krishna

Hi,
see this wiki
RSXMB_ARCHIVE_MESSAGES Archive XML Messages
RSXMB_CANCEL_NOT_REST_MESSAGES Cancel XI Messages With Errors That Cannot Be Restarted
RSXMB_DELETE_ARCHIVED_MESSAGES Delete Archived XML Messages
RSXMB_DELETE_MESSAGES Delete XML Messages from the Persistency Layer marked for DEL
RSXMB_CANCEL_MESSAGES Mass cancellation of error messages - XI
RSXMB_SHOW_REORG_STATUS & RSXMB_SHOW_STATUS provide an overview for all XML messages in XI persistency layer.
RSXMB_MESSAGE_STATISTICS2 which provides the processing statistics. This report basically analyzed the history table.
RXWF_XI_UNSED_MSGS report helps in converting messages states other than 003 to final state i.e. 003.
SXMS_REFRESH_ADAPTER_STATUS report helps in converting message sates like 001/008 into final state.
http://wiki.sdn.sap.com/wiki/display/XI/PIArchivingConceptual+Overview

Messages stuck at Adapter engine

Hi everyone,
My messages are getting stuck at the Adapter engine level and shows the status as "Holding". But the step at Integration engine seems to work fine.
How could i get rid of these messages, before I run another couple of messages.
Also what could be the reason for the error.
Thanks,
Vinotha M
Edited by: Vinotha M on Feb 23, 2009 5:59 PM

Hi Vinotha,
Apart from the blogs mentioned above dont forget to go through
http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/content.htm
This would give you a greater insight into your the cause and analysis of your problem.
Apart from the above link to avoid further cropping of the same problem you can " Start Prioritizing the Processing of Messages" http://help.sap.com/saphelp_nwpi71/helpdata/en/46/6ffe8effc20eede10000000a155369/content.htm
Rgds
joel
Edited by: joel trinidade on Feb 24, 2009 9:55 AM

Messages Stuck in adapter engine but passing through Integration engine

Hi All,
SOAPFault Error. Error Code/Category: XI Protocol/ Wrong Value...Received HTTP Response Code 500: Error during Parsing of SOAP Header
Above error as system error appears in adapter engine when messages are coming into SAP PI. At sender, we are having sender mail adapter.
Adapter Modules are also configured in mail adapter.What could be the possible reason.
Please suggest
Regards,
Kanisha

Below is the error log. As per scenario, Mail To File.
Please Suggest
Regards,
Kanisha

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

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

Message struck in adapter engine with status Hold

Hi,
In intergaration engine all messages are processed, I have checked SMQ1, SMQ2 (no message is struck in queue)
where as messages struck in adapter engine with status Hold, I have checked this in RWB. How to resolve this?
Regards,
Krishna

Hello,
Below is some information on how to resolve this type of issue:
1 - In the RWB, expand the tray for "Configure Table Columns" - by clicking on a square at the right end of this heading.
2 - Check the checkboxes for "Serialization Context" and "Sequence Number". These should then appear in the table columns as well.
3 - Add the Serialization Context to the Extended Filter Criteria. Search the messages in status HOLD based on this new additional criteria.
4 - Sort the messages in ascending order based on the Sequence no.
5 - Check the predecessor message of the first message in status "HOLD"
Based on the following status for this predecessor messages, the actions that can be taken for the HOLD messages are:
a - Predecessor is in Failed State/System Error : Cancel/Resend the
first message in status HOLD after this. Then the remaining messages
can be cancelled/resent.
b - Predecessor is in DLVD state(delivered state) : First Holding
message can be resent/cancelled followed by the others.
c - Predecessor is in NDLV(Non-Delivered Status) : Check why the
predecessor message failed and correct the reason for the failure.
Then resend the predecessor message and then cancel/resend the
remaining HOLD messages. Alternatively, you can directly try
resending this NDLV predecessor message and see if it goes. If it
goes, then the remaining HOLD messages can be resent/cancelled.
Another option could be to cancel this NDLV predecessor message so
that it goes to FAILED state and then cancel/resend remaining HOLD
messages.
Regards,
Sarah

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

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

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,

Message Monitoring with status delivering

Hello,
I have an scenario R/3 (Proxy) -> XI -> File.
Alls is successful in sxmb_moni, and there is nothing in SMQ1 and SMQ2, but in message monitoring ( adapter engine ) the message appears in status delivering.
The quality of service is exactly once. I checked the adapter and is in green status and the in the log the last message is Success The message status set to DLNG.
I've been searching for old messages, but for the same interface all the messages are with status delivering.
I can't cancel or resend the messages. Then I do the update but after that when I try to resend I obtain the same message "Update the status".
The adapter is an FTP connection with Connect Mode "Permanently".
Do you know what could be the problem and how to solve it? All the messages we send are in delivering status.
Many thanks in advance.
Regards,
Xavier.

Hi Xavier Carbonell ,
i also faced same problem. In my case some other Communication channels were in error state so all messages are struct in Messaging System, all my messages status went "To be Delivering". Please check all ur Communication channels are in green.
For futher information check the below link.
Flat file with two separators
If it is still not solved then restart J2EE engine.
Thanks,
Venkatesh
Edited by: venkatesh bs on Apr 14, 2008 12:09 PM

XI Adapter ? No messages in the adapter engine in RWB

Hi Guys,
I have the scenario SOAP-PROXY. I have configured XI Adapter on the receiver side. I have used xml spy to post the messages directly to the IS. I could not see any messages in the adapter engine in RWB.
I have seen the messages processed successfully in the integration engine under RWB.
can anybody explain why i could not see any messages in the adapter engine ? Is It normal with the xi adapter on the receiver side ?
Thanks,
Raj
Message was edited by:
raj reddy

Raghu.
I've done the following:
1. I've executed SE38 tx code.
2. I've entered the "RSXMB_DELETE_MESSAGES" report as "Program"
3. As the "RSXMB_DELETE_MESSAGES" report does not have a selection screen, it must be executed with default parameters. So, I selected "Program -> Execute -> Background".
4. There are no available variants, so I clicked on the "Execute immed." button.
5. The job starts. I can monitor it on the SM37 tx code.
6. It only deleted 20 messages.
What I get from this, is that the "RSXMB_DELETE_MESSAGES" report cannot delete the big part of the messages since them are marked as "Archivable" and not as "Archived".
what do you think of it??
regards
Carlos.

How to get Payload of SOAP Message in Advance Adapter Engine

HI All,
I am wondering if anybody can tell me how to view the Payload of SOAP Sender and Receiver Message in Advance Adapter Engine?
Does Anybody know how to check mapping payload in Advance Adapter Engine because in ABAP you can see the mapping payload under Request Message Mapping but when you use AAE you can't see the Request Message Mapping Payload.
I have a SOAP to RFC Scenario in which I can't see the SOAP Sender and RFC Receiver Mapping Payload.
When I am sending incorrect data to an RFC I am getting this error which is very strange and new to me.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to split a synchronous message
Any comments would be much appreciated.
Thanks,
Iqbal

HI All,
I have managed to find Michal's Blog which is talking about getting the mapping payload but unfortunately I don't know how to create Adapter Module so I am wondering if somebody can please provide me EAR file so that I will request the Basis guys to deploy the code and hopefully this will solve my query.
Michal's Blog
As you all probably know while using local Advanced Adapter Engine (AAE) processing in SAP PI 7.1 the message is logged only once (during processing by sender adapter). This is great in terms of performance but what if we need to check the mapping output? Is there a way do do it somehow? It turns out that we don't have such an option in standard yet. Is there any alternative then?
It turns out there is - a simplest adapter module there is...
Local AAE works in such a way that from the sender adapter it executes the receiver adapter so in the outbound message to PI processing you can see the adapter info logs of the receiver adapter and this is what we can use. The idea is to add an adapter module to the receiver adapter which will put the content of the message into the audit log of PI message processing. We can do it by writing a few lines of code:
PI/XI: target message logging with local AAE not possible ? not anymore...
*Please upload the file in any free site or <REMOVED BY MODERATOR>
<READ RULES OF ENGAGEMENT>
Thanks,
Edited by: Prateek Raj Srivastava on Jan 6, 2012 9:10 PM

Message split on adapter engine for the java based IDoc adapter

Hi Guys,
Do you know if message split on adapter engine is available for the java based IDoc adapter on the single stack (PI 7.31)?
I'm getting such exception when I try to post 3 IDocs
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDocXML for type <ns0:Messages>:
state=EXPECTING_IMMEDIATE_TAG_END, charPosition=68, lineNumber=1, columnNumber=69, invalidChar=U+0078,
sourceSnippet=...UTF-8" standalone="no"?><ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><...
^
Mapping is one to many.
Each IDoc content has been compared manually against the xsd schema and it was fine.
I know that old way of modifying xsd is still possible.
Best regards,
Wojciech

Did you find a solution to this? Having a similar error right now.
Thanks and kind regards
Jens

Message stuck in Adapter Engine queue with status "Delivering"

Similar Messages

Maybe you are looking for