Adapter Engine Holding Status

Hi,
I am working on an automation of XI message monitoring which includes checking the Adapater engine Holding count.
From where can I fetch the number of messages with HOLDING status.
Regards,
Karthik

Hi,
Just go to Run Time workbench (RWB) from your Integration Builder and then click on message monitoring --> then select the Database from dropdwon box ---> then from filter option "Status" select the "Holding" and press the start button and you will get your restult.
Regards,
Sarvesh

Similar Messages

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

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

Component Monitoing - Adapter engine XP1 status RED

Hi All,
Component monitoring link is incorrect. The URL references the WebDispatcher instead of the XI server. How to analyze this situation ?
Please advise.
Regards
Shiva

Hi,
Try with this...
http://<host>:<port>/rwb/index.jsp
Ramesh

Monitoring EOIO Messages stuck in AE with HOLD status?

Hi Gurus,
Scenario: IDOC -- > XI (Message split) - - > (HTTP/File)
Some times messages to File adapter are stuck in Adapter Engine with status "HOLD". Found the root cause and un-checked "Maintain order at runtime" in interface determination.
How to get alert if the EOIO messages are stuck in AE with status "HOLD"?
Please help.

Hi,
HOLD status
This is an EOIO message whose predecessor was not processed successfully yet. The status is retained until all predecessors are delivered successfully. If a predecessor has the "System error" status and is restarted, all successors are also restarted provided that the delivery of the predecessor is successful.
If a predecessor has the "canceled with errors" status, further processing is not possible in systems before Support Package 11 for the adapter framework and Support Package 10 for the adapter framework core patch 02. In higher version systems, the status of predecessors can only be set to "canceled with errors" in a manual way. Successors that have the "Holding" status can be restarted after you have set the "canceled with errors" status (see related note 811864).
Regards,
Sreenivas

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?

Unable to cancel messages in adapter engine

Hello,
We have implemented an interface with file connector. Since one week, all messages are hanged in the adapter engine with status TO BE DELIVERED.
I tried to cancel but the folowing error message appears :
Could not fail message. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not fail message 0013211d-2dc8-1def-a8a4-938b4635c3af(INBOUND), as triggered by admin action. Reason: Predecessor not in final state.
This interface is a proxy from ECC6-->csv file and i can't see the corresponding messaging in any queues SMQ1..
They are only available in the RWB/message monitoring/adapter engine
Can you tell me how to process these messages or cancel ?
Regards

Hi
Messages will go in to the state Tobe delivered if there are no threads available for the particular adapter.. and lack of threads is due to the state of the messages in DLNG...
Check the messages which are in DLNG and the reason behing long time for processing the same..(can be restart of the target system...)
if you get the error saying predecessor is not in final state...
for this you need to check the parent message in the queue which is causing this. this can be done using messaging system url
http://host:port/MessagingSystem/
go here and check the tab EOIO message ..... and there check the messages which are blocked and check the queue names if need to find the paticular queue..and reprocess if the error occured can be rectified...
HTH
Rajesh

Looping message in Adapter Engine

Hello!
We had a message which went fine in mapping (IDOC -> proxy) / integration engine (check flags in sxi_monitor) but stopped in Adapter Engine with status "To be delivered". No jammed queues or anything. It didnt help to restart the message, it was just looping. We had to restart one of the PXI-servers and after that it worked succesfully.
Any ideas what could have caused this or how I can fault-trace / debug this?!

Hi Stefan,
To be Delivered can happen because of two reasons:
1. PI Performance due to sudden heavy loads OR
2. in this case Receiver system Perfomance may be the case ..
pls check once with the receiver system performance .. and also the note suggested above(1623356) which mentions thread increase for that particular adapter type.
I hope this will help..
Thanks,
Praveen

Delete records in status holding on Adapter Engine

Hi all
We are running on XI 3.0 and Netweaver 04 with SP20 installed
I had a problem with a lot of message in status holding on Adapter Engine (develoment system)
I'm not able to restart (resend) or delete this message. I had look around on SDN and in SAP notes, and only found a lot of old stuff, but nothing there can solve my problem
This are a snapshoot of the error log
Success Processing child message of multi-message with message ID 3aa40608-c251-4845-209c-d327ba444b7c
Success Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLD.
Success Admin action: Trying to redeliver message.
Success The message status set to TBDL.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLD.
Success The message status set to TBDL.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLD.
Success Admin action: Trying to fail message.
Error Admin action: Setting the message status to 'failed' failed, due to: java.lang.Exception: Predecessor not in final state.. Success Admin action: Trying to redeliver message.
Success The message status set to TBDL.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLDError Admin action: Setting the message status to 'failed' failed, due to: java.lang.Exception: Predecessor not in final state..
Success Admin action: Trying to redeliver message.
Success The message status set to TBDL.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLD
Kind regards
Kim

Hi,
Change the combination in message monitoring, this time chose Ingegration Engine & Database combination and if you have messages in holding then try to cancel them but first find and delete the system error messages if any.
If you get success here then change back the combination to Adapter Engine & Databse and then try to delete it again.
I am sure that it is possible coz same problem was there with me and then after doing some R&D I was able to delete them.
Regards,
Sarvesh

Status "HOLDING" in RWB----- MessageMonitoring------ Adapter Engine?

Hi Experts,
I am working on a IDOC to file Scenario.
Sometimes the scenario works perfectly and the files are generated successfull
Somtimes the status of the messages are "HOLDING" in RWB--->MessageMonitoring---->Adapter Engine(Messages from the component)?
Why is this inconsistency ? What may be the reason.?
Thanks in Advance,
Anil

HI,
Holding state says that your QOS is EOIO.
If any message is not processed successful,
then next all message is all holding state.
Go throgh this link how to handle these messages
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
Regards
Sridhar Goli

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

Messages are in hold in the Adapter Engine

Hi all,
I am seeing in my adapter engine that all of the messages are in status hold , it is for a specific business system and interface.
2009-02-10 21:41:30 Success Message successfully put into the queue.
2009-02-10 21:41:31 Success The message was successfully retrieved from the receive queue.
2009-02-10 21:41:31 Success The message status set to HOLD.
can anyone please help?
Thanks in advance
Sugata B

Hi
i ve got the same problem .
I m using the message monitor in order to find the first message in error in this queue and so to be able to free the queue.
My problem is how to detect these holding messages.
As the error is in the Adapter Engine , you cant see it in sxmb_moni transaction
In the message monitoring, you can check it manually.
I need to have an automatic report of 'holding messages".
I try to connect the Adapter engine alert to the ccms. The problem is that autoreaction alert arent possible in this case.
Any body found the means to check directly in the database with sql-based command the status of message ?
thanks for your help
florent

How to process stucked holding messages in the Adapter Engine.

Hi experts,
This question is may be familier to all...
There are thousands of messages are in holding status in the Adapter engine in RWB.
I tried to found system error in these messages. There is no system error from the last in my investigation. I tried to restart of the communication channels of the combination of these messages. But it is also not use to fix this problem.
Instead of the restart of the Java engine please let me know is there any possibility to fix this issue.
Regards
Mahesh

Hello Mahesh
You can try restarting some of the XI services (e.g. com.sap.aii.af.svc) but usually a java restart is required to free up these blocked threads/queues.
Most likely these messages are in Holding status because there is a blockage in one of the Adapter queues. This can be monitored in the RWB
-> Component Monitoring
-> Adatper Engine XIP
-> Engine Status
-> Additional Data
Find out what adapter queues are causing the blockage and increase the number of threads/queues available to it. This will help prevent the issue occuring again.
See note #791655 Documentation of the XI Messaging System Service Properties, for an explaination of the queues.
See these blogs for more details:
1) /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
2) /people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements
Ensure note #937159 XI Adapter Engine is stuck, has been applied.
Regards
Mark

Help!Cache status of object for Central Adapter Engine is incorrect

this problem cconfused me several days!
version:PI 7.1
after i activate the communication channel, the cache not update for central adapter engine
problem: in cache status overview, the update for central adapter engine not yet started, but notification is ok.
the update for integration server and mapping run time are all correct.
then when i display wsdl for sender agreement(SOAP sender), show message:Cache status of object abcd123 for Central Adapter Engine is incorrect
if i ignore this message, error message popup:dapter Engine af.xid.sapittest for communication channel abcd123 not registered in SLD
who can help me solve this problem.
thank you in advance.

Hi cheng,
Kindly check if you have set theparameter 'com.sap.aii.connect.integrationserver.sld.name' in your
Exchange Profile, since it's not set by default. Open note #1278563 and follow the procedures.
And you may check the following notes:
#1031321 - Self-Registration of Adapter Engine and RWB fails
#1334053 - No automatic PI 7.10 SLD Registration (Here you'll see the note 764176 which you have already applied and also the note #1117249).
In RWB, is the adapter Engine "red light"? If yes, what is the specific error?
Regards,
Caio Cagnani

Adapter Engine Holding Status

Similar Messages

Maybe you are looking for