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.

Similar Messages

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

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

XI message status at Adapter engine level using a table (SAP table)

Hello Experts,
XI message status at Adapter engine level using a table (SAP table).
We want to write a custom report using ABAP so Pls tell why the status u2018Holdingu2019 and u2018To be deliveredu2019 are present in message monitoring of RWB but not in the status (MSGSTATE) field of SXMSPMAST table.
My need is to write a report to get the messages based on the these status from table level.
Please let me know the table name and field name for this and the table name for the desciption of the status of XI messages at Adapter level.
Thanks
Gopesh

Hi Gopesh,
the Adapter Engine Messaging System messages are on the Java schema,
i.e., see the following -
[XI/PI tables|https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/xi+tables]
Regards
Kenny

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

Message statuses in Adapter Engine

Hi,
Do we have any statuses of the message in Adapter engine?
Just a weird doubt...
Thanks,
Monica

Ok..
Assume that i have a scenario where in I need to update some data in MS SQL from SAP.
For instance, some one pushed junk data from SAP,(but this data is matching to our XML structures) and before I update this data in MS SQL, i need to validate data by connecting through JDBC adapter.
Now when I connect to database using JDBC, is it possible for me to validate the data in the adapter and if data is invalid, how can I update the IDoc status that data is erroneous?
Thanks

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 in Delivering status

Guys,
How do you stop messages running in scheduled state with status 'Delivering\.
It is been in that status for couple of days.
Am still getting error 239, connection refused from receiver FTP server.
When i checked their log, it was in FIN_WAIT2 status.
Please share light on this.

Hi,
" to be delivered" status may be because of following reasons:
-Receiver is not available
-Queue hang-up: check out SMQ2 for the message queue status
-try to restart the messages from the RWB-->Message Monitoring
-try out the accessibility of NFS folder from the PI server
-Re-activate the Receiver file channel with Receiver agreement..
for more on the Adapter Engine log, you can check this from the Visual Admin- log files
Regards
Aashish Sinha
PS : reward points if helpful

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

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.

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.

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

Similar Messages

Maybe you are looking for