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

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 are in schedule state in adapter engine

Hi PI Gurus,
In Production system, I have a proxy to JDBC scenario (Using AAE).
From ECC messages are flowing successfully, but when I check the WRB I found no message.
When I checked the Message Monitoring I found, those messages were in schedule state. No logs are also maintained.
Any idea, what is the reason.
This scenerio is working fine in QA and Dev.
Thanks,
Krishna

Hi krishna
Monitor your JDBC communication channel in CC monitoring , if you found any error in CC , then take an action accordingly.
if CC status was gree then check JDBC Adapter Service in NetWeaver Administrator and stop and start it
otherwise can you please check the status of message in sxi_monitor and also check if it is stuck in smq2? Let us know what error you getting in sxmb_moni or the flag of message. As suggested above, check the status of communication channel of JDBC adapter and what errors you getting there if any.
check this link;/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Edited by: haribabu.karasala on Jul 13, 2011 8:03 AM
Regards
Hari
Edited by: haribabu.karasala on Jul 13, 2011 8:04 AM

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

How to process stucked holding messages in the Adapter Engine.

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

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

Message Archiving for the Adapter Engine

Hi,
we have configured archiving for Integration Engine (SXMB_MONI) messages on the Production XI System. is it necessary to configure Message Archiving for the Adapter Engine also ? in which scenarios archived adapter messages are useful ? are there any other advantages/disadvantages for this(in case of errored messages on the adapter engine) ? Please share any ideas.
Thanks
Pavan.

>>is it necessary to configure Message Archiving for the Adapter Engine also
Not necessary,but depends upon the scenario,lets say you are posting messages to external partner's FTP and there was some issue in connectivity due to which file was not delivered,in this case you need to send the message again.
same thing can happen in inbound messages too.
>>in which scenarios archived adapter messages are useful ?
i would do this specifically for JDBC sender coz once you pick up the files based upon SQL query,you change the flag so that those values are not picked next time,in this case you can't re-run the old query and get same results.
this also holds for proxies and file too.
Thanx
Aamir

XI Adapter ? No messages in the adapter engine in RWB

Hi Guys,
I have the scenario SOAP-PROXY. I have configured XI Adapter on the receiver side. I have used xml spy to post the messages directly to the IS. I could not see any messages in the adapter engine in RWB.
I have seen the messages processed successfully in the integration engine under RWB.
can anybody explain why i could not see any messages in the adapter engine ? Is It normal with the xi adapter on the receiver side ?
Thanks,
Raj
Message was edited by:
raj reddy

Raghu.
I've done the following:
1. I've executed SE38 tx code.
2. I've entered the "RSXMB_DELETE_MESSAGES" report as "Program"
3. As the "RSXMB_DELETE_MESSAGES" report does not have a selection screen, it must be executed with default parameters. So, I selected "Program -> Execute -> Background".
4. There are no available variants, so I clicked on the "Execute immed." button.
5. The job starts. I can monitor it on the SM37 tx code.
6. It only deleted 20 messages.
What I get from this, is that the "RSXMB_DELETE_MESSAGES" report cannot delete the big part of the messages since them are marked as "Archivable" and not as "Archived".
what do you think of it??
regards
Carlos.

Messages are in hold state due to one message at receiver JDBC adapter

Hello,
I am using a receiver JDBC adapter and trying to send an XML file which has an insert query to insert some data into the database i.e., Oracle 9i.
Here at the receiver side due to one message ( which is in to be delivered state) all other messages are got hold and waiting for long time.
I am getting the exceptions as this,
JDBC Adapter processing failed with Error processing request in sax parser: Error when executing statement for table/stored proc. 'FSASMGR.XTBL_KL06_IINQUIRY' (structure 'REC01'): java.sql.SQLException: ORA-12899: value too large for column "FSASMGR"."XTBL_KL06_IINQUIRY"."CASE_TITLE" (actual: 81, maximum: 80)
Exception caught when executing statement for table/stored proc. 'FSASMGR.XTBL_KL01_ISTAFF_MST' (structure 'REC1'):
java.sql.SQLException: ORA-00001: unique constraint (FSASMGR.XTBL_KL01_ISTAFF_MST) violated
Can anyone help me out in solving this issue.
THanks,
Soorya

hi surya,
jdbc channel tries a request for n number of times(no of rettries),if that request fails it will take up the following requests,its not like it will process a request forever.
to be delivered will be resulting if reciever is down or network between XI and database server is bad.
try to ping databse server from XI host system.
if everything is fine then look at the channel configuration->advanced->no of retries of database transaction on sql server.
just redue the count to 1 and recheck.
Regards,
rama Krishna

How to remove large message stuck in the adapter engine?

Hi experts,
We have a large message abt 100 MB stuck in the adapter engine which is causing the J2EE server to restart continuously.
I have tried increasing the heap sizes and the number of threads in config tool, but no luck. My question here is how to remove that message? Also I checked smq1 and smq2 both are empty.
Regards.

Hi Nagasatya,
This issue is realted to Large amount of data.You have to write condition in the query.I have face same issue,but resolved it.Please do the following steps.
Go to Configtool and selct the com.sap.aii.adapter.jdbc.svc and set this jdbc service to start manually instead of auto.
Then restart server0, this time it should be started successfully. Then go to rwb and try to
find if any jdbc hanging/failed messages are there, if so, cancel them;also deactivate the problematic jdbc communication channel, otherwise itwill poll the data again. After all above, you can manually try to start this jdbc.svc particually.
Thanks
Ravi

Getting error in the adapter engine when sending a message

Hi,
I'm always getting this error in the adapter engine: Message processing failed. Cause: com.sap.aii.messaging.util.URI$MalformedURIException: no scheme
The comm channel ends up in error because of messages having the above error.
Could someone please help?
Thanks.
Mike

Mike.
Please check this links.
Check your adapter and restarted.
com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number
Re: Prerequisites to setup configure mail scenario.
error in communication channel
Error :Receiver File Channel not Initialized

Messages goes into scheduled status in adapter engine

Hi all
we are doing idoc to file scenario with direct mapping. the messages are getting processed in integration engine sucessfully. the messages are getting into scheduled status in the adapter engine even when there is less load in the server.
Thiis specially happening for IDOC to file scenario only. Any help is highly appreciated
Thanks

>
> the system is quite good at the moment but the some of the messages again into scheduled status like ( 10 out of 1000 messages ) . the system is not performing at 100 % rate since some messages moves to scheduled status. Is still the performance can be improved in any other ways ?
>
This is really strange behaviour , If Communictaion channel functioning correctly then all succesfull messages should deliver to Receiver system.
Better to check payload of scheduled messages(if wrong payload obiously it goes schedule status),try to to reprocess them.
I never used XCOPY command,so no comment on that.
Regards,
Raj

Messages are in HOLD state

Hello ALL,
We have all messages processed sucessfully in Monitor but in "HOLD" state in the Audit log...EO is the QOS...Not sure why the messages are in HOLD state..There are atleast 15 receivers for this interface..ANy ideas guys..
-Teresa

Hi Teresa,
Which SP do you work with?
note: 813993
"<b>If a predecessor has the "canceled with errors"
status, further processing is not possible in systems
before Support Package 11</b> for the adapter framework
and Support Package 10 for the adapter framework core patch 02."
last time we talked you were on SP4 so
maybe you need OSS to handle this...
unless you've upgreaded
BTW
Are you sure it's not EOIO?
if it's EO then the predecessors thing doesn't make sense... wierd
>>>" Can't award points--Forum error"...
maybe they are changing our Martix...
Regards,
michal

Alerts in the Adapter engine

Hi all
I´m working in a BPM scenario, I have raised an alert from the BPM and it arrives to my inbox(alert framework). And also i can see it in the CCMS. But now I trying to configure an alert to be raised in case of an error in the Adapter engine (file adapter). I´m on sp15 and i have create a alert categorie and an alert rule setting this with the value Adapter engine and the adapter type File.
I have checked the alert with "RSALERTTEST" and it works fine it arrive to my alert inbox and to the ccms. But i have an error in the file adapter and is not arriving anything. The communication channel is a Sender. There is some thing missing in my configuration?
Any help please?
Regards
Noelia

Here are my hints:
1) http://help.sap.com
Alert Notification Step-by-Step
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Alert Configuration
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
2) Michal's blog: XI FAQ
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
XI: Alerts - Troubleshooting guide
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
XI: Alerts - Step by step
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
3) Notes:
750287 XI 3.0 Runtime Workbench: Alert configuration does not start
768456 Troubleshooting Runtime Workbench XI 3.0
813703 XI RWB alert configuration is incompletely displayed
840849 XI 3.0 Runtime Workbench: SSO2 is not active in this system
824039 XI30 Runtime Workbench: Display of XI alerts in CCMS
0000906044 XI30 Alerting: Wrong hostanme in the URL of the XI Alert
0000905896 XI30 Alerting: Message without recipient creates no alert
0000904825 Synchronous message processing: Error in CCMS connection
0000902022 XI30 Alertrule insensitive to Receiver Interface
0000882215 XI 3.0 Runtime Wkbnch: Java Adaptr does not generate alerts
0000876546 XI 3.0 Runtime Workbench: Missing alerts
0000870232 XI 3.0 Runtime Workbench: New Alerting functionality
But start with this one:
913858 XI3.0 Alerting: Troubleshooting
4) User roles
SAP_ALM_CUSTOMIZER -- Alert Management: Role for Customizing
SAP_ALM_ADMINISTRATOR -- Alert Management Administrator
SAP_BC_ALM_ALERT_USER -- ALM: Role for the alert user
SAP_BC_ALM_ADMIN
SAP_BC_ALM_CUST
SAP_XI_RWB_SERV_USER
SAP_XI_RWB_SERV_USER_MAIN
Regards,
Sandro

Changing Exactly-Once-in-Order Processing in the Adapter Engine

During some issues with hanging messages in some communication channels I noticed that messages for other receivers were also on hold. So adapter engine was processing all messages EOIO while Integration Server does that per receiver.
I found the [solution in the SAP Help |http://help.sap.com/saphelp_nw04/helpdata/en/45/13b942f14d29efe10000000a114a6b/content.htm] but I am not able to access the mentioned link: http://<host><port>/MessagingSystem/migration.jsp
Error message I got is: 404 not found.
Looks like something changed! I checked some simular links like http://<host>:50000/MessagingSystem/monitor/monitor.jsp and that works fine.
(I also checked the role SAP_XI_ADMINISTRATOR_J2EE was included in my userprofile)
Please help me finding what I do wrong...or what has changed.

Hi Sunil,
ok, but do you know how what happened with the
http://<host>:50000/MessagingSystem/migration.jsp
I need that link to change the EOIO processing in the adapter engine.
Regards,
Michel

Error while reading access data (URL, user,password) for the Adapter Engine

Hi,
Any idea on below message? I am doing file to file scenario and got the below tarce from sxmb_moni.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.pi1.piserver1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.pi1.piserver1</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.pi1.piserver1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Balaji

It looks like the adapter engine is not able to register him self on SLD, you have to check in the SLD the "Exchange Infrastructure" domain, you have to verify restarting the J2EE the adapter engine update the entries in the SLD related to the specific XI Domain.
Launch Visual Administrator >> Server >> Services >> SAP AF CPA Cache
Enter the appropriate values for:
SLD.selfregistration.hostname (Use fully qualified hostname)
SLD.selfregistration.httpPort
SLD.selfregistration.httpsPort
Sandro

Messages are in hold in the Adapter Engine

Similar Messages

Maybe you are looking for