Message status "Holding" - Message monitoring adapter framework

Hello,
We have some messages with the status "Holding" in a queue in the message monitoring in the adapter framework.
Normally you have to restart the first message of that queue. The message with the status "system error". Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I already read the blog about "[How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1887311350DB01819286872323159351End?blog=/pub/wlg/3566]"
The blog does not mention what to do when the first message (sequential number) is not available anymore.
Is it possible to restart the messages in the queue in that case?
Thanks
Kind regards
Frank

Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I assume that the message was deleted.....in this case the next message in the queue will be blocking the queue....so try resending this message....even the blog mentions that you either solve the error or cancel the message....so now start from the second message....if possible solve the error for this message....if not possible to resolve then cancel it so that rest of the queue gets processed
From the blog:
Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and
resend or cancel the message to release the queue.
Regards,
Abhishek.

Similar Messages

Purging EOIO messages with status "Holding" at the adapter level in XI.

Hi,
I want to purge a set of messages (some 800) with status "Holding" at Adapter level in RunTime Workbench. I have gone through the blog "/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework which explain the way to reprocess the messages which are stuck in EOIO so that the rest in queue are processed but is there a way to purge a large number of messages in a EOIO queue which are holding for long, at the adpater framework level thorugh some option in Runtime workbench or Visual Administrator of J2EE server on which XI is running ?

Hi Gourav,
What do you mean by delete files from folder.
I have this problem and I can't get rid of the messages that are stuck in the adapter engine.
If I need step 3. how is that done?
Thanks.

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

JDBC Messages in Holding state

Hi all,
My scenario is jdbc to jdbc - get data from an stored procedure and execute some updates in other database system. What is happening that today all update messages (jdbc receiver) are set as sucessifull processed in sxmb_moni, but no information was updated in target database. I saw that in RWB, those messages are with status "holding"... some of you has any idea how can I deal with this?
thanks!
roberti

Hi,
This might help you
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Messages in "holding "status in Adapter engine
Regards
Agasthuri Doss

Holding Message in AFW!!!

Hi guys,
I have a message in Holding status in AFW
SAP help tells me this definition:
HOLDING:
The state of an EOIO message that cannot be delivered until its predecessors have been delivered.
Anyone knows whats happening and how can I reprocess it again?
Thanks in advance,
Ricardo.

hi,
have a look at Stefan's weblog:
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
to see how to deal with it
Regards,
michal

PI : Message Status Description ?

Hi,
Please advise where i can get detail information / description on the PI Message status below :
Integration Server :
Message Status
==============
Message Status:      000
Message Status:      001
Message Status:      002
Message Status:      003
Message Status:      004
Message Status:      005
Message Status:      006
Message Status:      007
Message Status:      008
Message Status:      009
Message Status:      010
Message Status:      011
Message Status:      012
Message Status:      013
Message Status:      014
Message Status:      015
Message Status:      016
Message Status:      017
Message Status:      018
Message Status:      019
Message Status:      020
Message Status:      021
Message Status:      022
Message Status:      023
Message Status:      024
Message Status:      025
Message Status:      026
Message Status:      027
Message Status:      028
Message Status:      029
Message Status:      030
Adapter Status
==============
Adapter Status:      000
Adapter Status:      001
Adapter Status:      002
Adapter Status:      003
Adapter Status:      004
Adapter Status:      005
Adapter Status:      006
Adapter Status:      007
Adapter Status:      008
Adapter Status:      009
Adapter Status:      010
Best Regards
Fernand

Hi Ravi,
Thank You for your helpful asnwer, how about adapter status ? is that the same like Integration Server Status ?
Best Regards
Fernand

XI messages status "Message scheduled on outbound side" with Green flag

Dear,
          On My XI system , i have too old messages and i want to clear those.
          In moni messages status is "Message scheduled on outbound side" with Green flag .
         When i am trying to cancel these messages i am getting a popup saying
          "Cannot cancel message because of it's status"
          And there is no queue entries for these messsage on smq1 or smq2 (perhaps deleted by someone)
          I just want to cancel these messages, please tell me if there is any way .
Thanks in Advance,
Sandeep

Dear Sunil,
                Thanks, these meesages are neither active nor used anywhere,
                Problem is somebody has manually deleted entries for these messages from SMQ1 and SMQ2.
Regards,
Sandeep

Adapter Framework File Adapter Message on hold

Hello,
we have a problem with the Adapter Framework and their the File Adapter / Messaging System.
We process one HR IDOC from R/3 through XI and send it to 7 file adapters. The SXMB_MONI tells us that all messages have been processed without errors and when you go to the RWB and use the Message-Monitoring many messages are on status HOLD. XI makes the message EOIO once you have multiple receivers and something blocks the messages in the AF. Is there a way to delete the AF queues like the XI queues with SMQ1 or SMQ2. It looks like SAP had duplicated the SMQ business in JAVA but I found no documentation how to clean up queues or what to do if the get stuck.
Thanks
Stefan

hi,
you can try question 3 adapters section
on the XI FAQ:
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
to see adapters in RWB
but if you see them when you do it then
it means that this XI's configuration was not complete
so you may expect further problems
Regards,
michal

Adapter message monitoring: message in HOLD

Hi,
since we changed a scenario:
a) old scenario: R/3 --> XI --> BPM --> XI --> FTP
b) new scenario R/3 --> XI --> FTP
the messages stuck in adapter message monitoring.
Message-Interface is the same, CC is the same; just the way through BPM was canceled.
any suggestions?
Thanks
Regards Mario

Hi Mario,
messages are in status HOLD, when they need to be sent in exact order (EOIO), and an error occured in one (or more) queues. When you solve this error, restart the first message from the queue after this error and the items will be processed.
How to do that:
Go to messaging system servlet, find your message (in hold status) and click the Eye icon - Details. Now read the Conversation ID value - which is your queue ID.
Go to RWB, message monitoring, choose adapter engine( from combobox)-> display.Now click additional criteria, put the value of Conversation ID to conversation ID textbox. Start search. You'll see a lot of messages there in hold status I think, But find the one in System Error status. Try to resend this message, if it will not change its status (will still be in in System error), cancel it. Now restart first message from the queue, which was after this wrong one.
This should release the queue and process items.
If any questions, let me know.
Peter

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

Stuck in To Be Delivered Status in Message Monitoring - Adapter Engine

Hi,
I have messages stuck in To Be Delivered status in Messages Monitoring. When i checked the Audito Logs, there are NO LOGS. I resent the message and now the logs indicated in the Audit Logs is:
2014-03-26 08:39:10
Information
The message was successfully received by the messaging system. Protocol: XI URL: http://<host>:<port>/MessagingSystem/receive/AFW/XI Credential (User): PIIXXXX
2014-03-26 08:39:10
Information
Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2014-03-26 08:39:10
Information
Message successfully put into the queue.
2014-03-26 08:52:48
Information
Admin action: Trying to redeliver message.
The connection between the receiver is ok, does this have something to do with the Communication Channels?
Please help.
thank you.

Hi Eng Swee,
there are messages that were cancelled yesterday and the status is 'Terminated With Errors'
this is what is indicated in the Audit Logs
2014-03-26 02:38:47
Information
Admin action: Trying to fail message.
2014-03-26 02:38:47
Error
The message status was set to FAIL.
2014-03-26 02:38:47
Information
Admin action: The message was successfully set to status failed.
2014-03-26 02:38:47
Error
Asynchronous error detected: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Message failed by admin.. Trying to report it.
2014-03-26 02:38:47
Error
Asynchronous error reported.
Is this the reason why the messages are stuck?
thank you!

Messages remain in Scheduled status in message monitoring in RWB

Hi PI experts,
I have got a situation where there are several messages showing in the Scheduled status. I followed the path RWB > Message Monitoring > Adapter Engine > Database (Overview) > Display.
QoS for these messages is EOIO, however there are no messages stuck in the queue. All other channels are running smoothly. Only with this particular channel the messages remain in Scheduled status for a long time.
I am neither able to make out the roor cause nor reprocess/resend these messages. Pleaes help.
Regards,
Dhawal

Hi Suraj,
What you said is absolutely correct. However, as I mentioned, the error message was not visible in RWB.
My problem just got resolved. What I did is this,
I followed the link http://<server>:<port>/MessagingSystem/monitor/monitor.jsp which is SAP Message Display Tool.
Here in EOIO Sequence Monitor I found the error message and it's predecessor. When I resent the erroneous message from here, all subsequent Holding messages got processed.
Thank you everyone for your help. Have a gr8 day...
Best Regards,
Dhawal

Messages stuck in queue AFWRecv of Adapter Framework

Hello,
Messages stuck in queue AFWRecv of Adapter Framework in our production system(trace in RWB: "to be delivered")
in URL http://xxxxxxx:50000/MessagingSystem/monitor/systemStatus.jsp we can see:
Queue Info
Queue Name isStarted QueueSize ThreadCount (working) MaxThreads
AFWCall true 0 0 (0) 20
AFWRecv true 954 10 (10) 10
AFWRqst true 0 0 (0) 20
AFWSend true 0 0 (0) 10
We have tried to resend the first message but that´the result:
Time Stamp Status Description
2010-10-09 11:24:06 Success The message was successfully received by the messaging system. Profile: XI URL: http://xxxxxxxxx:8100/MessagingSystem/receive/AFW/XI
2010-10-09 11:24:06 Success Using connection AFW. Trying to put the message into the receive queue.
2010-10-09 11:24:06 Success Message successfully put into the queue.
2010-10-11 00:01:46 Success Recovering from loss of connection to database; message loaded into queue by recover job: System Job (Failover Recovery)
2010-10-11 02:48:16 Success System Startup: Message successfully loaded into queue: AFWRecv.
2010-10-13 11:03:19 Success Admin action: Trying to redeliver message.
2010-10-13 11:03:46 Success Admin action: Trying to redeliver message.
Since then it stucks there...
Any help would be apreciated....

Hi,
Go to the runtime workbench --> Message Monitoring --> Click on the 'Configure Table Columns' > Check Sequence ID, Serialization Context & Sequential Number options.> and then click 'Apply'.
Then in the 'Serialization Context' column you will get the queue ID for the stcuk message.
Take that value and click on the 'Show additional Criteria' option on the top and put this value in the 'Serialization context' parameter. Also,select the start/end date as 'This year' --> start.
You will get all the messages stuck in that particular queue for this yoear, try to rectify them, so that your message will be processed.
-Supriya.

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

Message in status 'holding' without reasonable reason

Hi all,
I will explain this 'X file' problem.
We have an scenary between an R/3 --> XI --> R/3
The communication it's between an interface with .txt file; No conversion to XML, XI only does 2 steps at Interface Determination:
1º Writes in an FTP destination with Communication Channel Filereceiver
2º Executes an RFC who charges that file in a table at destination.
The interface sends between 100 and 200 files by day. At least 2 / 4 by day stays in status 'Holding'. These files are similar to another Succesfull messages.
At Integration Server, and SXMB_MONI, all logs are OK. But in Adapter Engine from RWB i see this log (For File CC and RFC CC):
2007-12-11 15:53:41     Success     Message successfully received by messaging system. Profile: XI URL: http://xixsap:59000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-12-11 15:53:41     Success     Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-12-11 15:53:41     Success     Message successfully put into the queue.
2007-12-11 15:53:41     Success     The message was successfully retrieved from the receive queue.
2007-12-11 15:53:41     Success     The message status set to HOLD.
If we make a "Resend", the message tries to be delivered again and sets to Hold.
If i resend the same file from original /out directory, it's processed fine.
Thanks in advance for your help
Message was edited by:
        Federico Martin
Message was edited by:
        Federico Martin

Hi Federico,
Holding is the state of an EOIO message that cannot be delivered until its predecessors have been delivered.
When the quality of service of the messages is exactly once in order (EOIO) and messages are delivered in the same sequence that they were sent from the sender system. For that reason a sequential number is assigned to the message.
When a message runs on an error during the processing, all other messages in the same queue will not be processed until the error is fixed or the erroneous message is cancelled from processing.
To solve the problem it is necessary to
1.find the message which blocks the queue.
2.If there are a huge number of messages in your system you search for the lowest sequential number in the queue.
3. If you know the name of the queue that is stuck, you can add the queue name as additional filter criteria. Click on Show Additional Criteria.
4. Enter the queue name to the field Conversation ID and set the parameter Quality of Service to Exactly Once in Order.
5. To be able to see the sequential numbers in the message monitor, you configure the table columns.
6. Add Conversation Id (that is the queue name) and Sequential Number to the table columns.
7. Scroll the window right to see the new columns. Sort the sequential number ascending (the upper triangle).
8Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and resend or cancel the message to release the queue.
9. After you have resent or cancelled the message all other message will be processed immediately.
You have of course to make sure, that the next message in sequence does not run on error too.
**Pls: Reward with Points if helpful **
Regards,
Jyoti

Message status "Holding" - Message monitoring adapter framework

Similar Messages

Maybe you are looking for