To Be delivered status in Message monitoring

Hi,
There are some messages in TO BE DELIVERED status in Message monitoring while selecting integration server. I could neither cancel nor resend.
any input reg. this will be appreciated.
I didn't see any messages with TO BE delivered status in adapater engine.
I could able to clear What ever messages in system error status in adapter engine by filtering based on sequential id.
I have seen this thread & link also.
To Be Delivered
Re: "To be delivered" status in RWB -- Any solution?
http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/content.htm
I could not see any entry in SMQ1, SMQ2, SM58 also
Thanks
Praba
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:02 PM
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:04 PM

Hi,
You cannot resend or cancell the messages which are in status "To Be Delivered". Check Receiver adapter File/Jdbc/ OFTP e.t.c. which is processing these messages.
Check with your Basis team to remove the lock of adapters if any. Or to process these messages you require soft restart of Java stack.
I had same kind of issue two days back with OFTP adapter messages and did soft restart of java stack with help of Basis team.
Hope it will helps you
Cheers
Veera

Similar Messages

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!

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.

Delivering Status in Messaging system

Hi,
I am monitoring messages in messaging system. I can see some message status as "Delivering" from so many days. I am unable to delete those messages. It is not even changing to undelivered status. Please help.
Thanks,
Gunasree

Hi Gunasree,
The messages in the DELIVERING status can not be cancelled. The messages might have gone to delivering stage due to many reasons. If some earlier message got failed in the queue or the connection between the Receiver and adapter engine break...or some other reason.
For messages in the delivering status it can be cancelled by stopping the adapter engine only.
Thanks
Ajay

To Be Delivered Status for messages

Hi All,
I've a File->PI-File scenario. If I check the status of messages under RWB->Message Monitoring->Adapter Engine, I find some mesages with status "Scheduled". The single status of the messages is "To be delivered". Manually I try to send a single message but in the Audit Log I find "Admin action: Trying to redeliver message."
The Queue "DispatchDisp" is fill with all the messages.
How can I send these messages?
Thanks in advance
2009-02-11 17:11:20 Information Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2009-02-11 17:11:20 Information Message successfully put into the queue.
2009-02-11 21:13:15 Information Admin action: Trying to redeliver message.
2009-02-11 21:14:29 Information Admin action: Trying to redeliver message.

Your file is stuck in a queue where failed files are waiting to get resolved. So you need to clear the queues first and then process your file.
Here is the way to clear the queues for Failed messages with System Errors.
RWB --> Adapter Engine --> show additional criteria --> Enter the QUEUE NAME in field "Conversation_ID" (for this you have to first know the queue name from details of the messages having ststaus "Holding" or "to be delivered".) --> Expand "Configure table columns" --> choose "Conversation ID" and "Sequential Number" --> display. --> sort the list by ascending order of "sequential number" --> cancel the message whose sequential number is latest and go on canceling in ascending order.
Hope it helps.
Br,
Madan Agrawal

'System Error' status at Message Monitoring( HTTP to FILE )

I have created a scenario HTTP to FTP. I sent message to XI server using the HTTP Client.
After sending the message I am getting the response at browser.
Result:
http-Status: 200 Message accepted
Payload:
But when I look in to the Message monitoring at RWB, I am getting the message status as
System error. while going to the details i can see below error category.
Error Category MAPPING
Error Code EXCEPTION_DURING_EXECUTE
(Is the password different for port 50000 and 8000)
Please help me to solve this issue.
Thanks in Advance,
John

This is the trace message that I got for this error
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:72) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>

Want to access Status in Message Monitoring

Dear All,
I want to get access to the Status Parameter in Message Monitoring so that depending on the Status(Waiting or Syste Error),I can set my logic and send a mail to the developer.
I need help.
<b>1. Where can I find out the Parameter for status in RWB Message Monitoring?
2.Is there any method so that I can set some parameters and it will directly send mail to the developer or I have to use Mail Adapter and write my own scenario?
3.If I am to develop my own scenario,then how to automate the whole process for each of the New messages?</b>
Thank you in Advance.
Sugata

Hi Suresh,
Thank you for your reply.But this is not what I wanted.In my RWB,there are different Message monitoring Status parameters and I want to get hold of that,to be more open,I want that status to come as Subject of my mail.For that reason I need the Status Parameter,and I need to put that in my mail.How to do that?
Cheers..
Sugata

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.

BPM wait step : RWB"To Be Delivered status": SXMB_MONI"Message being sent"

Hi All,
I have a BPM interface running fine since 1 year.
In this BPM I have wait step for 5 minutes.
But yesterday message is stopped on wait and not proceeding ahead.
I checked XML is good as per mapping. and in runtime wirk bench message is still in "To Be Delivered status"
and in SXMB_MONI message column Outbound Status still showing "Message being sent" even after 12 hours.(wait is only 5 minutes). And below is the trace of last message.
Please guide how to handle or restart this message. in SMQ1 & SMQ2 there are no queues showing:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>
Regards

Solved, few BASIS jobs were inactive in transaction code "SWF_XI_CUSTOMIZING".

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

Scheduled Status in Message Monitoring

Hi All,
We have a scenario from DB- DB using Java Proxies. The Message interfaces are defined as Asynchornously with EO mode.
Usually the sender channel picks data and tirggers Java Proxy. Proxy process all records and send the status back to sender in 5 mins.
But when I started multiple interfaces at the same time, I observe that one interface is taking 15 min and while that interface is in processing state, the other interface which started at that time are also in Scheduled status. But the sender channel picks data for every 5 mins, which is creating duplicate records.
The interfaces which are in Scheduled status are getting processed only after that interface ( taking 15 min) gets processed.
Why is this dependency on other interfaces and is there any way to avoid this dependency?
Please suggest.
Regards,
Srini

you can do queue/message prioritization.
but I suggest to use one status field in DB, when you are polling DB to select records , immidiately change staus to picked and after processing successfully change it to processed.

Message monitoring Status Waiting for email receiver

Hi Guru,
Scenario: SAP ECC will call Error Handling interface class. The communication channel for the Error Handling interface is Email Adapter.
Below is CC setting:
Adapter Type: Mail (Receiver)
Transport Protocol: SMTP
Message Protocol: XIALL
Adapter Engine: Integration Server
URL: smtp://11.11.11.111/
Check - Configure User Authentication
User : user1
Password: password
Mail Attributes:
From: [email protected]
To : [email protected]
Subject : test
Content Encoding: base64
I encountered one problem where my email receiver status in message monitoring is always 'Waiting'. I do not know what went wrong in the setting? Does anyone know how to solve my problem ?
Thanks in advance.
Regards

XI tries 3 times before changing the status of the message to System Error. One can Manually resend the error messages by using the RESEND button in RWB. In scenarios where XI was trying to send the message to an end system that was down for maintenance, you would want XI to resubmit the message automatically without human intervention. What would be nice is to able to tune the retries like IS_Retry which is available for Integration engine.
We can achieve this by changing the retry count used by the Adapter Engine, by default its set to 3 times, 5 minutes apart. This count can be changed in Visual Admin->server->services-> SAP XI Adapter: XI.
Here change the number Retries parameter from 3 to 10 and change the retry retryInterval to around 10minutes. For these configuration changes to be picked up, restart SAP XI Adapter: XI.
please visit the blog
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

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

Messages stuck in TO BE DELIVERED status

Hi !
Suddenly, whenever a message has to use the File Adapter, no mather which communication channel is to be used, the message is stuck with the "TO BE DELIVERED" status.
These messages, all have SUCCESSFUL status in the SXMB_MONI. The problem is in adapter engine. ALL have NO errors in their Audit Log. Because the problem is in adapter engine/framework, obviously queues at SMQR/SMQ1/SMQ2 are emtpy. ALL have QoS = EO (no eoio queue is used, NO predecessor messages are stuck with system error).
This occurs no mather which adapter is the sender (RFC, File, etc.)
The audit log is:
2008-04-10 16:59:34
Success
Message successfully received by messaging system. Profile: XI URL: http://xxxxxxx:yyyyy/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-04-10 16:59:34
Success
Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-04-10 16:59:34
Success
Message successfully put into the queue.
If we try to resend the message using the "resend" button in RWB, the message keeps in the TBDL state and the only difference is a new "success" entry in the audit log saying that:}
"Success | Admin action: Trying to redeliver message".
We already refreshed the cache and restarted the Java stack.
Any clues?
Thanks !
Regards,
Matias.

Hi,
Statuses such as HOLDING or FAILED usually happen only for delivery semantics EOIO (exactly once in order) or BE (best effort means Asynchronous). TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue. This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
The MS returns HTTP 200 to the Integration Server only if this was executed successfully. In this example scenario, status TO_BE_DELIVERED should not appear since we assume that the IS has called the servlet successfully.
The status is updated from TO_BE_DELIVERED to DELIVERING when the message has popped out of the receive queue and the event handler lookup was successful, so there is a small gap where TO_BE_DELIVERED could remain in the message monitor, although it was delivered from IS successfully.
Regards,
Srini

Messages are in to be delivered status

Many messages are in to be delivered status in the adapter engine message monitoring
Can any body help regarding this

Hi Sandeep,
     Would you explain a little bit more your issue?
     i.e:
     This kind of messages are Sync Messages?
     Do you have more than one message in Interfaces Determination object?
     If multiple inbound interfaces are assigned by the interface determination, the messages are forwarded according to the quality of service Exactly Once in Order (EOIO) at runtime. This means that the order in which the inbound interfaces are entered in the interface determination determines the order in which the messages are received.
     You can change this default by deselecting the Maintain Order at Runtime checkbox. In this case, the quality of service Exactly Once (EO) is used to forward the message to the inbound interfaces.
Regards,
Luis Diego

To Be delivered status in Message monitoring

Similar Messages

Maybe you are looking for