Adapter Engine queues

Hi all,
XI is sending messages (several interfaces) to an external system.
For some interfaces this external system needs a lot of time to return the http response back. Thus the waiting queues are generated on AE. From log files I see that there are five such queues. At the certain point (heavy traffic) all messages have to wait in these queues regardless their interfaces.
To avoid that, I would like to have separated queues on AE based on interfaces: Messages that belong to one interface would go into one queue, messages of another interface into another queue and so on.
I am talking about AE, on IE I donu2019t expect waiting queues.
I donu2019t want to use EOIO since I donu2019t want that the queue is stopped in case of an error.
Could you please advice?
Thanks, Janos

Hi,
in SXMB_ADM you can define filters and priorization for queues.
Means, you can specify separated queues for specific interfaces.
Cheers,
André

Similar Messages

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,

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

Adapter Engine Message in Delivering Status

Hi All,
Any idea how to cancel/delete the messages which are in delivering status in Adapter Engine.
In my case a single EOIO message is stuck in the AE with delivering status. Other messages are flowing successfully using the same cc.
Earlier during such cases we had to restart j2ee/ stop/start AF Messaging to resolve the problem.
Just wondering if theres any other solution?
btw : The message was in delivering status because the password mentioned in the receiver channel was wrong. There were other messages which failed but the status of those messages went into "System Error". Nothing wrong with that, but just wondering why did a single message remain in the "Delivering" status.
I have already been through this thread Re: How to delete message in "Delivering" status. Only exists in Adapter Engine and didnt find/understand anything which could help me.
Thanks
Sumit

Look at these blogs,
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework : How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
XI : How to Re-Process failed XI Messages Automatically
Message stuck in Adapter Engine queue with status "Delivering"
Hope this helps

Delay of Message in the Adapter Engine when put into queue

Hi XI/PI Experts,
We are having problems in the Adapter Engine wherein messages are staying longer in the AE queue as usual. Sometimes, it stays longer in Delivering status also. Is there any way we can monitor and try to push the message out of AE to avoid delays? I know we can do this in the ABAP side (Integration Engine)...but how can we do this in the Adapter Engine?
See below sample logs in AE RWB:
2008-07-17 13:28:13 Success Using connection SOAP*****. Trying to put the message into the receive queue.
2008-07-17 13:28:13 Success Message successfully put into the queue.
2008-07-17 13:34:12 Success The message was successfully retrieved from the receive queue.
2008-07-17 13:34:12 Success The message status set to DLNG.
As you can see there is a gap of 4 minutes.
Hope you can help me. Thank you so much in advance.
Grace

Hi.
Thanks for your answers but the messages are not set into EOIO but just EO. So the messages are not ending up in Holding Status.
I also believe that issue is not occurring because of too many messages in error in AE nor because of the receiving system is down. Issue is happening when message is about to be sent to the SOAP communication channel in AE. As you can see in the sample log I provided above, in RWB AE, after the message was put into queue, it took several minutes to be delivered to corresponding comm channel. My questions are:
1. Is there a way we can monitor the queue in AE like the way we monitor the queue in IE? (e.g. smq1 and smq2 transactions) .
2. If there is a way, how are we going to intervene manually on the queues in AE? (we can intervene with smq1 and smq2 in IE)
3. For messages with Delivering Status in AE, sometimes it is taking hours to move to "Successful/Delivered" Status. Is there a way we can intervene with that? I believe we can resend messages with "System Error" Status and Staus "To be Delivered" but for status "Delivering"...it is not possible (from what I know -- I hope there is a way).
I look forward to hearing from you guys/gals.
Grace

Adapter Engine delay reading Queue

Hello,
Can anyone help me with the following:
Since a day or two we have been experiencing delays in message processing in the adapter engine. The delay is always in the same step when looking at a message via MDT:
2007-05-21 14:30:25 Success Message successfully put into the queue.
2007-05-21 15:33:33 Success The message was successfully retrieved from the receive queue.
Here there is a one hour gap for a step that normally takes only 1 second. The delay appears and disappears without intervention. On friday there was a delay of 45 minutes and yesterday it was one hour (always at the end of the afternoon).
Which queues does this regard? Are these the queues shown via this link? http://<server>:<port>/MessagingSystem/monitor/systemStatus.jsp
Sander

I think below SP19 (or is it 20) the file adapter and jdbc adapter share one of those four queues if same direction and same asynch/synch type. Pretty sure they split in 19 or 20.
You can increase max threads on the queues. It's in visual admin, but I can't remember exact parm at the moment (one is 'max consumers', or something similar).
We ended up creating a de-central AE to move high volume/low priority messages separate from low volume/high priority messages. It's was just our way of dealing with our mix of messages.

PI 7.0: Message prioritisation in adapter engine for SOAP adapter.

Hi All,
We have both high and low priority synchronous messages using the SOAP sender Channel of the Central AE.
How can we make sure that High Prio messages ALWAYS get a thread right away when entering the AE? Installing a separate AE is not an option.
When I look in RWB->Component Monitoring->Adapter Engine->Engine Status in the Queues tab, I see this:
SOAP_http://sap.com/xi/XI/SystemCall Yes 5(5) 5
SOAP_http://sap.com/xi/XI/SystemRqst Yes 5(5) 5
When a new High Prio message enters, it can take more than one hour before it gets processed, because there are 1000 Low Prio messages also using the same 5 available Threads...
This delay is of course unacceptable for High Prio messages.
I checked in many other threads in SDN, looks like we cannot priortise for particular messages in PI 7.0, as we can do only at adapter level, not at interface level.
I was thinking of going to the approach which was suggested by "Gr, Wout" in the below thread.
xi prioritization in adapter engine (ae, af, adapter framework, java, jca)
Creating own adapter "MYSOAP" by copying the metadata of SOAP adapter. By that we can use our own adapter "MYSOAP" for high priority interfaces.
what you think guys about this approach?
Is there any thing I need to take care going through this approach apart from copying SOAP metadata into my own adapter.?
Thanks
Deepthi

increased thread count for soap adapter

Installation and then Configuration of Plain J2se Adapter Engine

Hi All,
Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
this URL is there in our SLD but we are not able to access the page.
So Please can somebody help me to resolve this issue.
Thanks & Regards
Sathya

Hi Amol,
I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
"ERROR CALLING THE RESTART ADAPTER"
Also status is shown is yellow and version is shown as not set.
Where ever I have changed the configuration data I have shown it in bold
JMS-Adapter Configurarion
This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
Set XI message protocol version. This sample is designed for XI 3.0
version=30
JMS message receiver class
classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
set if a transacted JMS Session should be used (default: true)
#JMSSession.sessionTransacted=false
set delay in milliseconds before processing next message after an error (default: 0)
errorDelay=10000
#set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
#reconnectDelay=10000
set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
#TransportMessage.type=TransportMessage
TransportMessage.type=XMBMessage
uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
insert your class here for an individual binding between JMS and Transport Message
uncomment the following line for using Bindings that belong to Tunneling
#transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
uncomment the following line for using Bindings that belong to Single Payload Binding
transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
be started if messages are exchanged otherwise ID logs won't be created anyway
eoExpirationAfterDays=365
garbageCollectorInterval=86400000
#
the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
configured in case of A2A scenarios.
#XI.SenderParty=Sender
XI.SenderService=MQSeries
#XI.ReceiverParty=Receiver
XI.ReceiverService=MTX
XI.InterfaceNamespace=http://xitest
XI.Interface=MI_Out_File
XI.TraceLevel=1
XI.LoggingLevel=1
XI.QualityOfService=EO
XI.QueueId=ABCD
XI.ContentType=text/xml
# *************************************************************************************************************
#
URL of XI IS to send the messages to
XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
XI.User=XIAF
XI.Password=XIPASS
# *************************************************************************************************************
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
# uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=xisuper
JMS.QueueConnectionFactoryImpl.password=xxx
#
uncomment and adjust parameters for loading JMS administrated objects via JNDI
uncomment and adjust parameters if not the default context should be used
#JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
#JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
#JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
#JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
set the Lookup Names
#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
#JMS.FileNameQueue=SAPQueue.ser
uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
JMS.QueueImpl.classname= progress.message.jclient.Queue
JMS.QueueImpl.constructor=java.lang.String SampleQ1
# uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String JAVA.CHANNEL
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String postcard
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
# *************************************************************************************************************
uncomment and adjust parameters for using a dispatcher ***
#Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
#Dispatcher.namespace=namespace1
#namespace1.ConversionDispatcher.logPayload=true
#namespace1.Service.1=Plain2XMLService
#namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
#namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
#namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
#namespace1.Plain2XMLService.xml.fieldNames=a,b,c
#namespace1.Plain2XMLService.xml.fieldSeparator=;
#namespace1.Service.2=XSLTService
#namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
#namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
Can you please help me in resolving the error.
Regards,

Configuration of JMS Adapter in Central Adapter Engine

Hi all,
I have configured Sender JMS Adapter in Central Adapter Engine with the following parameters:
Adapter type : JMS
Transport Protocol : WebSphere MQ (non-jms)
Message Protocol : JMS1.x
Adapter Engine : Integration Server
Queue Connection Factory java class :Com.ibm.mq.jms.MQQueueConnectionFactory
Queue java class : com.ibm.mq.jms.MQQueue
ipadd : localhost
port : 1414
Queue Manager name : TEST.QMGR
Channel Name : CH1
JMS Queue : LQ
CCSID : 437
Protocol : TCP/IP
JMS-compliant : WebSphere MQ(non-jms)
JMS Queue user : MUSR_MQADMIN
Mapping of message : Entire Message = JMS Payload
But the status is red with an error message Sender Details : NULL
Could you please tell me what went wrong?
Regards
Sathya

Hi,
Make sure that Websphere MQ server is running.
If u r comfortable with java, you can even write a Java code to acces the server and check if the JMS server is working fine. Some times there will be sample applications provided by Websphere MQ itself.
Once the java program works then it will be easy to debug the error over here.
Regards,
P.Venkat

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?

Messages are in To be delivered state in the Adapter engine

Hi,
For all the receiver file adapters the messages are successful processed through Integration Engine ,no messages are stuck in SMQ1 & SMQ2 on Inegration engine.
All the messages are stuck in Adapter Engine with the status "To be Delivered ". These are all asynchorus scenarios. The quality of service is also EO.
We restarted the J2EE engine also several times but no luck.
Did anyone had similar issue?
Thanks
Sachin

Hi,
Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords and tcode - SXMB_ADM and "active" the queue then the messages and check it out.
Regards
Agasthuri Doss

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

Adapter Engine queues

Similar Messages

Maybe you are looking for