API clean up and validation

Proper API clean up and close

EC allows different ways to handle API/MI programs and to get only the first data on an MI returning multiple records. As a result, unsent that data remain on TCP buffers of the BE and system resources are consumed. When you close API, the view shows a warning on releaseAPICaller. Then, EC reads the remaining data in the BE to clean it up and to save on system resources.

API checks and validation

Every MI connection in a pool that EC will reuse is verified first using the GetServerTime command. This verification consumes time and resources. You can skip this verification and specify a time frame when to run validate.

To define the time frame, edit the ec.properties file and add a numeric value in the MvxAPI.Pool.Connection.CheckAPI.Time property. The default value 0 (zero) means to always perform validate. For example, MvxAPI.Pool.Connection.CheckAPI.Time=10. In this example, EC validates the API that is not used within 10 seconds.