07.04.2015, 23:11 | #1 |
Участник
|
emeadaxsupport: Requesting large packages across AX AIF can result in timeout errors after 30 seconds regardless of your timeout values
Источник: http://blogs.msdn.com/b/axsupport/ar...ut-values.aspx
============== A common time out exception you may experience with NetTcp AIF calls in AX is: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '01:09:59.9770000'. This error can be deceptive as it doesn’t relate to actual timeout values but instead to the size of the ObjectGraph coming across through WCF. The workaround for this issue is to either break up your packages by sending multiple smaller requests, recommended, or by increasing the size of the MaxItemsInObjectGraph behavior parameter. Below are steps for increasing the object graph size for an AIF Inbound port service.
Источник: http://blogs.msdn.com/b/axsupport/ar...ut-values.aspx
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору. |
|
Теги |
aif |
|
|