WebService "OperationTimeout" doesn't really time out. Why?

serdarulutas

Hello,

I have an issue with NAV web service timeout setting.

We set the Web Services "OperationTimeout" property to 00:00:59 from original value "MaxValue" so web services calls would timeout in 59 seconds. I put a SLEEP(100 * 65) command at the end of the NAV function to make it wait enough. The web service-call indeed waited for one minutes and timed out. However, the NAV function seems to have continued running and the write operation is completed. My expectation was that the timeout interrupt NAV process and the changes would be rolled back. This didn't happen.

Any suggestions or comments on this? Maybe I am not doing something right.

Thanks


External Link : https://msdn.microsoft.com/en-us/library/dd355055.aspx

kriki

I noticed this too.

In theory, a webservice call should be fast within a few seconds.

For NAV, you can add a lot of code behind a call and let it take a long time before finishing. I (ab)used NAV webservices in NAV2009 by using them instead of the NAS. I put a command in SQL Server agent to call the NAV webservice to run jobs that before ran using the NAS (but the NAS was not really stable).
When I did my testing, I noticed that I had a timeout in SQL, but my logging in NAV showed me that the process was continuing.

So, I suppose it is normal.