Message sutck in TBDL in Adapter Engine

Hi all,
We use RequestResponseBean and ResponseOnewayBean in the conversion from Async RFC to Sync SOAP.
There was a big message load on this integration this morning. In the Adapter Message Monitoring, I found thousands of messages stuck in TBDL status. I checked in SMQ1 and SMQ2, there are no stuck queues.
Anyone knows the problem.
Thanks!
Regards,
Hui

hi,
I think there is some configuration error with the corresponding communication channel.

Similar Messages

Getting message Attempt to determine which Adapter Engines......

Hello All
1. I am Getting System message 'Attempt to determine which Adapter Engines are affected by data changes failed' in the Integration Directory.
Updating SOAP Adapter (Sender channel).
Refreshed all caches...
2. Also while testing using SOAP Test client getting response
HTTP/1.1 500 Internal Server Error
connection: close
set-cookie: JSESSIONID=(XIServerName_03)ID1387309050DB21025913116517472411End; Version=1; Path=/
set-cookie: saplb_*=(XIServerName_03)31556950; Version=1; Path=/
server: SAP J2EE Engine/6.40
content-type: text/xml; charset=utf-8
any idea?
Thanks in advance

Hi Naveen
Thanks for your reply...
Actaully previously sender channel was working fine, i just updated the default namespace in the channel.
I was getting the error because of wrong namespace in channel (Case sensitive).
So i updated this name space and after activation i am getting above message while testing.
Regards

Message do not exists in adapter engine

I have a message being sent to IE via JMS Adapter . In Communication channel monitoring i could see the message Id & error message(Error in converting Binary message) but with that message id i could not find any entry in Message monitoring - > Adatpter Engine. Moreover , In communication channel monitoring the id with which the message failed is not hyperlinked to "Message Display Tool (Detail Display) ".
I need the message which is failed.
Thanks ,
Satish

It may be possible that message came into error as soon as it was picked by the sender channel. Could you see some error for these messages in Communication channel monitoring? Another possibility is your message is persisted in the adapter engine for very short duration. In that case, if it is archived, you may select the Archive option in Message Monitoring instead of Database option.
Regards,
Prateek

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

Error resending messages with system-error in Adapter Engine

Hi all,
We got an error when trying to resend all messages in error in runtime workbench, message monitoring, adapter engine, database (overview), clicking on a sender service with messages in error state, and clicking on "repeat" button to resend those in error messages. The error is "No authorization to execute action for component Adapter Engine XP0". The user We are using to perform this task is associated to all groups available in CUA... some of you has any tips about how to perform this operation?
regards.
roberti

I really don't remember what solved this problem, but it is solved. Now the functionality works as it should.
Regards.
Waldemar Roberti

EO Messages with Delivering Status in Adapter Engine

Hi All,
We have a scenario DB-DB Asy with Java Proxies. Proxies are there to accept the messages from Sender DB and insert in target DB. Get the response from target DB and insert back that to Sender DB.
Actually the scenario is Syn, but we made it as Asynchronous by implementing Java Proxies.
Now we are using EO mode in Sender JDBC channel. We have 17 interfaces in the similar pattern. We are using one common XI receiver channel for all these 17 interfaces.
If one message got struck, then rest other Proxies are not getting triggered and not able to resend the message ( ofcourse I know I cannot resend with Delivering Status). But not sure what causes the messages to failed with Delivering Status mode.
Any pointers would be highly appreciated.
Will increase of Parallel Queues really solve my problem? If it fails in Prod, its a big problem for us as we dont want to lose the data. Now everytime we are restarting the Message service server.
Regards,
Srinivas

Normally if there is any problem in target then you will see the adapter engine message as delivering
after the no of retires set then status will go to system error
during this entry check the CC used what is the error causing for that ?
HTH
Rajesh

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

Message Id duplicated error in Adapter Engine

Hello guys,
last week we had an error in an adapter JDBC sender. The error we see in the adapter is: Error during commit or rollback of database transaction: 'com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to commit transaction: The transaction has been rolled back: com.sap.engine.services.ts.transaction.TxRollbackException'
If we see inside the error says that when is tryring to put the message in the queue the error is that the key message id is duplicated.
Searching in the message monitoring, there is a message processed with the same message id 3 hours before.
The problem was after a re-start of PI, and the solution was to create a copy of the adapter. we tried to start/stop, inactivate/activate and the error still continue, Ia have not tried to put the old adapter again.
Anybody knows what could be the problem or a correct solution?
Many thanks ind advance.
Regards,
Xavier.

Hi, Xavier
See note 1361305 - File sender adapter generates duplicate message IDs.
In my system, this note solved the same problem in JBDC and file adapter.
Regards,
Carme.

Messages are not reaching to Adapter Engine (JMS receiver)

Hi Friends,
We have one scenario running on Production env.
Scenario is: R3(IDOC) -> XI ->JMS Provider
IDOC to JMS.
Sometime we found messsages are successful in SXMB_MONI, but those messages entries are not found under AE.
Means they are not reaching to JMS.
Communication channel is green, without any error.
This happens sometime only, and no changes have been done to JMS adapter parameters.
What might have happen to these messages, which are successful in MONI but not visible under AE.(Even not in Archived option)?
I searched on SDN, but most of the questions are unanswered.
Please let me know your inputs.
Divyesh Vasani

Hi Divyesh,
check under message monitoring in RWB
if u r not finding the message there , those might be archived.
did u confirm with the destination system .. if they got the messages?
if at all messages are stuch in AE ... and if u search the correct message u should be able to see the message.
if the Integration engine unable to put messages in AE , then in some pipeline step in MONI it will show error

Message in "delivering" status in adapter engine

Hi All,
There is a message which is in the "delivering" queue long time ago(around 1 month) and I need to know:
what is the possible cause for this issue?
how to change the status to "successfull" or "failed"?
Any help will be really appreciated.
Thanks
Ivan

Hi,
If receiver communication channel is file ftp, then check SAP note num 821267, point 45:
45. Receiver File Adapter stuck while using temporary file.
Q :The thread of receiver file adapter remains in runnable while
       Communication channel has the following configuration
       File Construction Mode=Create, Overwrite Existing File=false,           Write Mode= Use Temporary File.
A :The Receiver file adapter thread is stuck in the runnable state when the temporary file is used and over writing of existing file is set to false. Since the temporary file was not being deleted and the overwriting of existing file i.e. target file was set to false, the thread would never end. This problem has been fixed by deleting the temporary file after being named to the target file.
           The error is corrected with SAPXIAF06P patch#8 (Support              Package -level #06).
Regards,
Carme.

Auto restart of messages failed in Adapter Engine PI 7.0 and 7.1

Hi,
I am trying to figure out a way to automatically restart the messages failed with in the adapter engine (because of the target system not available etc.). These messages are in System Error status and I can restart them from RWB. But I am looking for any report or something available either on Java or ABAP engines so that I can automate the process.
Thanks for the help.
VJ

I have come across the web service AdapterMessageMonitoring in PI 7.0 (Found it in Web service navigator) with possibly useful methods. But I could not find the same service on PI 7.1. Any clue on this?
Also, the getMessageList methods works perfectly as expected but the resendMessages mehtod fails with the exception -
com.sap.engine.services.ejb.exceptions.BaseEJBException xmlns:ns1="http://sap-j2ee-engine/client-runtime-error">Exception in method resendMessages.</ns1:com.sap.engine.services.ejb.exceptions.BaseEJBException>
Will post more if move forward.
VJ

Split Mapping message IDs in Adapter Engine

Hi Experts,
I have to get the message ID of all messages from adapter engine where these messages are created as a result of a split mapping.
I only have the inbound message ID in integration engine. Is there any place where this correlation is maintained.
Regards,
Ravi.

hi,
Check out this blog also:
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
Rgd, Adapter Engine:In general
http://help.sap.com/saphelp_nw70/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
Message Flow for some extent:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e21106cc-0c01-0010-db95-dbfc0ffd83b3
hope this may help you,
regards,
srinivas

Resend Message that fails in adapter engine but shows success in sxmb_moni

Hello SDN!!
We are testing sending soap requests out via SSL. We are using a BEA as a pass through server for SSL encryption only.
The scenerio is to send a message from SAP to PI 7.1 to BEA (SSL enc) to Receiving System. We successfully connect to BEA (only used as a pass-through) but the connection to Receiving System does not work. This returns an error to our adapter engine.
My question is this, Since SXMB_MONI shows the message as successful, but the adapter engine is showing an error. What is the best way for
1. Monitor the errors, (I only see where you can monitor the type of adapter only)
2. Resend the message, since it shows valid in SXMB_MONI, it won't let me resend.
Any help will be greatly appreciated and awarded
Cheers
Devlin

1. Once the message is in successful status in moni, the best way to monitor becomes RWB -> Message Monitoring.
2. For adapter engine related errors, you may resend the data manually using the resend option in the Message Monitoring. Otherwise, for automatic retry of messages, you may change the default settings.
Regards,
Prateek

Unable to cancel messages in adapter engine

Hello,
We have implemented an interface with file connector. Since one week, all messages are hanged in the adapter engine with status TO BE DELIVERED.
I tried to cancel but the folowing error message appears :
Could not fail message. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not fail message 0013211d-2dc8-1def-a8a4-938b4635c3af(INBOUND), as triggered by admin action. Reason: Predecessor not in final state.
This interface is a proxy from ECC6-->csv file and i can't see the corresponding messaging in any queues SMQ1..
They are only available in the RWB/message monitoring/adapter engine
Can you tell me how to process these messages or cancel ?
Regards

Hi
Messages will go in to the state Tobe delivered if there are no threads available for the particular adapter.. and lack of threads is due to the state of the messages in DLNG...
Check the messages which are in DLNG and the reason behing long time for processing the same..(can be restart of the target system...)
if you get the error saying predecessor is not in final state...
for this you need to check the parent message in the queue which is causing this. this can be done using messaging system url
http://host:port/MessagingSystem/
go here and check the tab EOIO message ..... and there check the messages which are blocked and check the queue names if need to find the paticular queue..and reprocess if the error occured can be rectified...
HTH
Rajesh

Messages taking few seconds to pass through Adapter Engine

Hi All,
I am dealing with Synchronous scenarios.Sender is SOAP adapter and receiver is proxy.
When I monitor the message monitoring audit log for Adapter engine I can see in the message is taking 4-5 seconds to reach the Integration engine from the SOAP sender adapter.
This delay is in the Audit log when the message goes from the step "Trying to put the message into the call queue" to "Message successfully put into the queue".
Is there any setting by which I can eliminate this delay time in adapter.
Can somebody help me out on this?
Note : CPU Utilisation is around 7 % and there are around 700000 messages per day.
Thanks,
Zabiulla

Zabiulla,
it's a performance tunning task. Unfortunately most of the actions SAP suggested for performance tunning are aimed at async communication, for SOAP, what you can at least try is to: Instead of using the SOAP sender adapter, you can directly send a SOAP request to the entry point of the Integration Engine pipeline bypassing the Adapter Engine. As a prerequisite, the URL/query string should include the XI parameters like in the example below:
http://<server>:<port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Try this to bypass adatper engine, this should help in your case.
Jayson

Message sutck in TBDL in Adapter Engine

Similar Messages

Maybe you are looking for