We have recently upgraded to FSM 6UPD9 to make use of the ODATA REST APIs in order to integrate our external applications with FSM.
Very often we are getting a request channel timeout while using the ODATA REST API’s. Once this starts every call fails.
Message:Error occurred while getting EDM model from app server.
System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9970047. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
The ODATA rest API's makes a call to the FSM server "<perform_get_updated_odata_edm>" to get the data model. It basically asks for the database table structure of ~1200 tables in FSM, which looks to be a very time-consuming operation. We have observed that the ODATA API attempts to refresh the EDM model every time there is a server restart/ IIS reset or whenever we do a refresh cache (full) from FSM smart client. The refresh cache is something we are doing every time we make any change using the FSM smart client.
Anyone else experiencing the same ? and is there any fix /workaround to this?