Better solution for Delivering messages

[Former Member]

Hello All,

In our prod environment, We observe quite often, when ever there is an issue at target side ,messages are failing and status in NDLV state in Adapter Engine ,apart from this NDLV state ,we observe few messages in Delivering state.

When the issue at target side get resolved.we are restarting NDLV (system error state ) messages from Adapter engine in RWB.

In order to process the Delivering messages ,we are restarting the message system to make the delivering messages to NDLV state.then we reprocessing those messages.

Because of this Messaging system restart to resolve the issue ,few more messsages failing during that time.

So for reprocessing the Delivering state message,Is there any possible way to handle this apart from restarting Messaging system.

Please provide inputs on this

Thanks and Regards,

Vidya Sagar

[Former Member]

I dont think with out the restart of the java stack DLNG messages will get cleared off..

options you can look for is possiblity of the target system maintenance schedule in advance and disable the particular channel

which will not work for hard shutdowns of target systems..i.e immediate shutdown cases..

Increase the no of threads for particular adapter queues..you can increase the thread count for the adapters based on the factors provided by the sap..which will not result in To be delivered messages..

HTH

Rajesh

[Former Member]

can you elaborate the activities you perform by saying "Restart the messaging System"

[Former Member]

XI Basis team handling this ,they are restarting the message system on the node which messages are in delivering state