In Message Monitoring Message showing holding status

Hi
Can anyone solve this problem.Its urgent for me.
My scenario is IDoc->XI->FILE
The file i am trying to generate is an xml file which i am dropping in XI application server using File system.
The problem is when i am going to see the message using transaction SXMB_MONI the perticular message interface is showing waiting for acknowladgement status .
But in message monitoring in runtime workbench the it is showing following status:
Adapter Engine
<b>Holding</b>
18.11.2005 05:42:09
CORP_SAP_DR2_030 http://limited.com/usa/sap_appl/retail/VendorsSAPAPOToMANU
MIIA_Create
BS_MANU
I am in SP14.
Also the output xml file is not getting created in the XI application server.
Please let me know the solution.
Thanks
Debraj Roy

Hi Debraj
HOLDING is a status which occurs normally for EOIO (Exactly Once In Order), so your message is set to Holding means some earlier message has not gone through. So until those messages are through this message will be in HOLDING state.
Have a look at this link which explains how to handle such scenarios.
http://help.sap.com/saphelp_nw04/helpdata/en/49/e3fb40ef74f823e10000000a155106/content.htm
cheers
Sameer
Assign points if it helped you

Similar Messages

Showing Holding Status in RWB

Hi Friends
I am stuck up in this problem have gone through the blogs but of no use...
Actually I am working on a Idoc to File scenario and sometime before a scenario which was working fine stop working after a small change in the mapping.
I am unable to get the file in my target system even though there is no error in the IR and ID .
In the RWB it is showing me no error but the component Monitoring is showing the status as "HOLDING"
I have removed the messages with status system error and now there are only 2 types of status one is HOLDING and another is SUCCESSFUL.
Any help would be surely rewrded with points.
Thanks and Regards

Hi,
Actually the problem is not in XI side, it is at receiver end.
Possible cause of holding status.
1. If you are sending a text file then check your FCC parameters. As you said it was working fine, but after you made some changes in mapping and form then it is not working.
Check if you have added or removed any field in mapping the FCC will change accordingly.
2. It may happen that Receiving System is not available/up. Plz chk this too.
Regards,
Sarvesh

Message got struck in hold status in message monitoring.

Hi SDNers,
             I am doing Idoc to File scenario. I triggered an Idoc and it is successfully processed in XI and got struck in message monitoring with hold status.
             After repetetive attempts of restarting the message, still it is in hold status.
             Even if I tried to cancel the message, it is not cancelling as it is in hold status.
            Can anybody please help how to process the message or can anybody explain how to cancel the message from message monitoring, which is in hold status.
Regards,
Jayaram.G

Hi,
If the message that has not yet been delivered is not in error state, the problem cause is probably that the message is blocked in the QRFC queues of the Integration Engine.
Check queue status
Call the Integration Server and call transaction SMQR in the sender and receiver Integration Engine in the corresponding system client.
Check the status of the scheduler and the status of the XBQ* and XBT* queues:
u25CF     Inbound qQueues
XBTI* (ExactlyOnce)
XBQI* (ExactlyOnceInOrder)
u25CF     Outbound queues
XBTO* (ExactlyOnce)
XBQO* (ExactlyOnceInOrder)
u25CF     Acknowledgment queues
XBTB* (ExactlyOnce)
XBQB* (ExactlyOnceInOrder)
u25CF     Large message queue
XBTL* (ExactlyOnce)
If the scheduler has the status Waiting, it is waiting for free work processes. This is why delays occur when XML messages are processed.
If not all necessary queues are registered, you can search for queues with the name prefix above using transaction SMQ2. Use transaction SXMB_ADM to register the queues in this case.

In Message Monitoring Message showing Error:Message

Hi
Can anyone solve this problem.Its urgent for me.
My scenario is IDoc->XI->FILE
The file i am trying to generate is an xml file which i am dropping in XI application server using File system.
The problem is when i am going to see the message using transaction SXMB_MONI the perticular message interface is showing waiting for acknowladgement status .
But in message monitoring in runtime workbench the it is showing following status:
Adapter Engine
<b>Holding</b>
18.11.2005 05:42:09
CORP_SAP_DR2_030 http://limited.com/usa/sap_appl/retail/VendorsSAPAPOToMANU
MIIA_Create
BS_MANU
I am in SP14.
Also the output xml file is not getting created in the XI application server.
Please let me know the solution.
Thanks
Debraj Roy

hi debraj..
is ur mesage ie sxmb_moni in red staus or scheduled status...??
if in scheduled cud be errors with queues ...delete ur queues with tcodes : smq1 and smq2...
and also hopefully u must have configured ur idoc correctly..
https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
regards..
vishal

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

All messages on hold in message monitoring

Hi,
If all of sudden (SOAP to idoc) ..for all the messages in message monitoring is on HOLDING status for all the interfaces.
These interfaces were working fine earlier.
In adapter monitoring , adapters are fine.
i could not see anything SMq transaction also.
what are the possiblities to cause this kind of error?
Thanks

Hi Bhavesh,
It is exactly once in Order.
This is really useful info which u send.
I could not find conversion id and sequential number as stefan mentioned in that blog in my message monitoring in config. table columns(in extended filter criteria)
But already i tried to cancel the those messages as well as resend but i could not do.
I guess my user do not have access to that.
Any other inputs/useful blogs?
Thanks
Edited by: Raja on Aug 14, 2008 5:47 PM
Edited by: Raja on Aug 14, 2008 5:52 PM

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 in HOLDING status in AE

Hi All,
We have an issue with JDBC receiver EOIO messages, with messages going into HOLD status in AE , its a DEV environment :
1) We have tried checking for failed messages before these messages we donot have any failed messages before these messages just messages in HOLD..
2) we are not able to delete or cancel these messages , we get a message cannot delete the message ,
3) The message is doing a INSERT update to JDBC , JDBC connection is fine.

Hi Kiran,
Please let me know if your problem is fixed.
I'm also facing the same problem in our Testing system where many messages are going to HOLD Status and also there are no messages in the System Error state.
We are trying to resend all the messages in every "Conversation ID". After this some messages gets successful and some will go into Waiting status. We then cancel the messages in waiting status and resend all the messages in HOLD status and the process continues till all the messages in HOLD status in every Coversation ID were cleared.
But this is a very very time consuming process.
So can you please let me know if there is any solution for this prolem.
Thanks,
Pruthvi

How to STOP messages going into HOLD status very frequently

I'm facing a problem in our Testing Environment where many messages are going to HOLD Status and also there are no messages in the System Error state.
We are trying to resend all the messages in every "Conversation ID". After this some messages gets successful and some will go into Waiting status. We then cancel the messages in waiting status and resend all the messages in HOLD status and the process continues till all the messages in HOLD status in every Coversation ID were cleared.
But this is a very very time consuming process.
So can you please let me know if there is any solution to fix this prolem.
Thanks,
Pruthvi

https://appleid.apple.com/cgi-bin/WebObjects/MyAppleId.woa/wa/directToSignIn?loc alang=en_US
Go the the above
Sign in. Go to the left side where it says phone numbers. Delete your number. Then save.
Your iPhone friends will now get the red exclamation point that the message didn't deliver instead of it sending. Then your iPhone friend will force the message to go through as a text by long pressing the message and choosing send as text. Once tthey do that once you're set and all other messages will automatically send as texts for them to you. You just have to hope your iPhone friends realize to force the messages through as texts the first time around but even if they don't at least they know they aren't reaching you and you aren't ignoring them.
Does that help?

SOAP messages not visible in RWB - Message Monitoring - Adapter Engine

Hi,
following scenario:
ERP is sending IDocs to PI.
Within PI an integration process sends the IDoc data through a SOAP (WS) receiver channel to a system far far away.
In RWB -> Communication Channel Monitoring I can see all delivered messages selecting my SOAP channel.
But:
I can´t see the SOAP messages in RWB -> Message Monitoring -> Messages of Adapter Engine.
In RWB -> Message Monitoring -> Messages of Integration Engine I only see SOAP messages with status "Error".
Successful column is empty.
Do I have to adjust some system / monitoring parameters also seeing SOAP messages in RWB->Message Monitoring?
Thanks in advance,
André

Hi Ravi,
thanks.
But there are thousands of successful messages delivered to the receiver.
These successful messages can only be seen in the Channel Monitoring.
I can´t find these successful messages in Message Monitoring.
Only some with status "Error" are displayed.
Strange...
Cheers,
André

Message monitoring of synchronous messages

Guys,
whenever I check a synchronous message in message monitoring, its audit log is correctly shown but the message (header and payload) are not shown, returning the message "The message was deleted to save memory" or something like that.
Does anyone knows how to enable message monitoring to show the messages from sync messages?
Thanks in advance,
Henrique.

Hi Henrique,
From SP12, the payload of sync messages is cached in memory rather than persisted. These payloads are deleted to prevent them from accumulating in memory.
You just have to set:
messaging.syncMessageRemover.removeBody = false
in the AF messaging service in the visual admin
and you'll be able to trace sync calls
you only need this for sync
if you set this you'll see sync messages in,
http://hostname:portnumber/MessagingSystem/monitor/monitor.jsp
(so in the monitor for adapters)
async are logged there by default so no need to change anything for async calls...
Regards,
Abhy
Message was edited by: Abhy Thomas

JDBC to JDBC error in receiver but success in message monitoring

Hi,
I got some doubt about message monitoring (SXMB_MONI), I have JDBC (DB2) to JDBC (Oracle) scenario. The message monitoring always show me success eventhough it has error when inserting to the target system (Oracle).
I am only can trace use Communication Channel Monitoring to known that my transaction actually failed.
Is there any workaround to this problem
Thank you and Best Regards
Fernand

Hi Raj,
The connection lost could be one of the possibility problem.
Can i use this scenario
Sender (JDBC, ansynchronous) -
> Receiver (JDBC, Synchronous), without BPM and then i still can see the message error whenever failed to insert into target system and restart the message.
or i have to use BPM for bridge between ansynchronous ---> synchronous mode.
Regards

Resend Message from Seeburger message monitoring

Hi friends,
I want to know that is there any possiblity of resending the message from Seeburger message monitoring tool.
One of the messages failed due to a problem in sender ID.
I want to resend this message. is it possible ?
Note: Message send out successfully from communcation channel to AS2 adapter.
Thanks
Sunil.

Hi Sunil,
Please let me know what error you can see in Seeburger Workbench.
In My view you can see the below type of error with State u201CError on send, will be retriedu201D
If Any Message failed in AS2 Adapter may be due to any reason
1. Wrong Sender/ Receiver ID
2. Wrong URL
3. Firewall rules are not in place
4. Partner Production site is down and you are unable to connect to him
Messages with above errors will appear with Success Flag in SXMB_MONI. But they will be caught by Seeburger Adapter and will be in the Error Status in SEEBURGER WORK BENCH
The only way to find/restart those messages is go to Runtime Work Bench Messages Monitoring --> Messages form Component (Adapter Engine) ---> System Error Status.
Any Message which failed in Seeburger Level can be seen only in Runtime Workbench.
Regards,
Rama.

Data Persistency in Message Monitoring of RWB

Hi All,
I am dealing with Sync. Interfaces and need to monitor the messages from Message Monitoring.
I have 2 Problems in the monitoring : -
1.     I can only see the messages for last 2 hrs in Message Monitoring.
        Messages Older then 2 hours are not getting displayed.
2.     Also if i am unable to see complete set messages in the 2 hr interval.I mean randomly
         messages are getting lost in message monitoring.
Is there any setting we need to maintain for Message Monitoring?
Helpful Answers will be rewarded points.
Thanks & Regards,
Zabiulla

Hi
have a look at this SAP Note 1031773 - Activating the message overview in RWB message monitoring
message struck in adapter eng.(RWB message monitoring)
http://help.sap.com/saphelp_nw70/helpdata/EN/45/0ea84637643c0ae10000000a11466f/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/be/38f0d8cbfe11d2a5f80060087832f8/frameset.htm
Thanks
Edited by: Abhishek Agrahari on Jan 8, 2009 8:14 AM

EOIO - Holding status

Hi,
I have an EOIO queue that is in status Holding. When I try cancel, it gives me error message "Unable to cancel 1 of 1 messages; update the status".
I am in XI 7.0
Regards
Unni

Hi Unni Krishnan,
        You must have in the message monitoring, a message that belongs to this interface that was defined as EOIO, that is in status System Error. Because of the EOIO(Exactly Once In Order), when a message that is in this quality of service stops in error, the subsequent messages stops with status Holding, that means that have a queue, waiting for the process of all messages EOIO in sequence(to grant that the messages will be delivered "In Order"), so you can´t cancel any message that is in Holding status, because this action would break the rules of EOIO.
        You need to find a message of the same interface, that is in the status System Error(probably), and cancel it(or reprocess it, if there are conditions to the message to be processed with sucess). So, the queue will start to process the next message, until end all the Holding messages. In the worst case(none of the messages have conditions to be processed with sucess), I think that you will need to cancel all the messages of this queue, one-to-one.
        Sorry my poor english, I hope that this message can help you.
        Best regards,
        Wilson

In Message Monitoring Message showing holding status

Similar Messages

Maybe you are looking for