Messages stucked "To be delivered" and "Delivering" Status.

[Former Member]

Hi,

Lots of messages are stucked in Adapter engine with status "To be delivered" and "Delivering" in our production system.

We found out there is some FTP connection problem with one of the interface which runs only few messages per day. Because of the problem of this interface, it is stopping many other critical interfaces to process and all these messages are falling "To be delivered" and "Delivering" status. All these interfaces are running in File adapters but going to different servers.

If there is problem with one server(One file adapter), why is it stopping all the other interfaces to process?

What might be the problem and how to solve it?

PS: As a temporary solution we are solving this issue by restarting the java stack.

Thanks

Deepthi.

[Former Member · Accepted solution]

Hi,

Check the below SAP Note Q.47

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267

Which talks about the maximum concurrency..which means that the threads can be controlled for a particular adapter..

As you said there are multiple ftp adapters and because of one its affecting all..

To avoid this the maximuum no of threads awarded to one adapter can be controlled so that the remaining threads can be used by other adapters...

For example...

Assume problematic adapter might be running for every 5 min...

Another adapters are running for every half an hour...

Before first run of another adapter , problematic adapter might have run for 5 times and occupies all 5 threads (thread wont get release as it will be in Delivering state...) remaining threads (another adapter threads) will go into ToBeDelivered state...

if you activate above parameters...only the assigned no of threads to particular adapter will be in Delivering (assume no as 2) then there will be 3 threads remaining which can be utilised by other adapters...

HTH

Rajesh

[Former Member · Accepted solution]

Perfect Rajesh.

That's the problem. Increased the threads for File adapter which solved the issue.

Thanks

Deepthi.

[Former Member]

Hi,

Suppose if in any of the queue on adapter engine, the message is failed, then the all messages coming to that queue after that will get stuck unless that failed message is cleared.

In your case also, I believe message has to be stuck in the concerned queue and hence, all other messages are stuck in 'To be delivered' status. You have to clear that message and then only these messages will be able to process.

As you already said, taking the restart of JAVA stack would be the last solution on this.

-Supriya.