Wednesday, November 16, 2011

XVP Messaging adapter hung for FTP TIMOUT

There was a scenario where the Rail Cargo messages stuck in the XVP system and every time we need to take a system restart in order to enable the server to process the messages again.

We checked the communication channel there also the FTP timout was 60 sec. Obviously, the messages stuck due to the FTP Timout but after that the messaging server was not able to process any of the message.

Root cause and work around suggested by David from XI team to set the value of parameter messaging.system.queueParallelism.maxReceivers to 2 for SAP XI AF Messaging and SAP XI AF Core adapters in visual admin.

We checked the value of the same was 2 in server0 but was 0 in server1. Change raised to correct the same in server1

For more information on messaging parameters follow below link:

http://help.sap.com/saphelp_nwpi71/helpdata/en/59/25ee41c334c717e10000000a155106/content.htm

Relevant material :
messaging.system.queueParallelism.maxReceivers
Value type: Integer

Default: 0 (disabled)

This property specifies the maximum number of parallel worker threads per queue, based on the receiver fields of the processed messages. A value of 2, for example, will limit the amount of parallel worker threads for one receiver channel instance to 2, allowing the remaining configured worker threads to process messages for other receiver channel instances of the same adapter type.

No comments: