Time-out error
In this document, we will use the information from the actual root cause analysis to make a generic view that can be used if you run into the same or a similar problem in the future. Finally, the document will describe the situation, the problem, the analysis, and the result.
Should you have any questions, please get in touch with academy@emagiz.com.
1. Situation
Specific time-outs occur on the entry flow where data is retrieved from a webservice before it is sent to the eMagiz flows towards an application
2. Problem
Data was missing for a certain time interval due to the time-out error.
3. Analysis
3.1 Reproduction
N/A
3.2 Analysis
The entry flow which caused the time-out was analalysed. It was found that there is no specific setting configured for influencing the duration before a time-out error is thrown. There is a specific setting for the bacoff period in the outbound HTTP gateway, which influence the time in between the different requests to the webservice but not the connection time-out itself.
4. Result
It is recommended to add a component to the flow that allows to extend the duration before a connection time-out is triggered by eMagiz. The component is called <HTTP Components message Sender>. The eMagiz default is 1 minute, and this component allows to extend that duration. Please review the log from the web service to find a suitable timeout setting. The backoff period might be changed to a lower value.