Skip to Content
Last modified by Erik Bakker on 2024/09/03 10:48
From version 13.1
edited by Erik Bakker
on 2022/06/13 16:11
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2022/06/13 16:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,8 +8,6 @@
8 8  * Last update: March 8th, 2022
9 9  * Required reading time: 3 minutes
10 10  
11 -===== Situation =====
12 -
13 13  == 3. Timeout occurred on a web service call ==
14 14  
15 15  === 3.1 Situation ===
... ... @@ -16,14 +16,10 @@
16 16  
17 17  At some point, questions were raised that the connection between eMagiz and an external SOAP web service ran into timeouts.
18 18  
19 -===== Problem =====
20 -
21 21  === 3.2 Problem ===
22 22  
23 23  Because the eMagiz solution ran into timeouts, data could not be synchronized between various systems within the integration landscape of the client. As a result, part of the functionality of the clients' systems was not functioning correctly.
24 24  
25 -===== Analysis =====
26 -
27 27  === 3.3 Analysis ===
28 28  
29 29  ==== 3.3.1 Errors in eMagiz ====
... ... @@ -36,8 +36,6 @@
36 36  
37 37  Once you have configured this to a value more extensive than the expected time it takes to finish the call, you will prevent the timeouts from occurring in eMagiz.
38 38  
39 -===== Result =====
40 -
41 41  === 3.4 Result ===
42 42  
43 43  The analysis concluded that adding a support object on flow level is needed to overwrite the default timeout setting of eMagiz of 1 minute. Once this is done, the timeout errors should be a thing of the past.