Skip to Content
Last modified by Erik Bakker on 2024/09/03 10:48
From version 16.1
edited by Erik Bakker
on 2022/06/14 08:08
Change comment: There is no comment for this version
To version 15.1
edited by Erik Bakker
on 2022/06/13 16:12
Change comment: Deleted image "rca-knowledgebase-timeout-occurred-on-webservice-call--http-components-message-sender.png"

Summary

Details

Page properties
Content
... ... @@ -8,17 +8,19 @@
8 8  * Last update: March 8th, 2022
9 9  * Required reading time: 3 minutes
10 10  
11 -== 1. Situation ==
11 +== 3. Timeout occurred on a web service call ==
12 12  
13 +=== 3.1 Situation ===
14 +
13 13  At some point, questions were raised that the connection between eMagiz and an external SOAP web service ran into timeouts.
14 14  
15 -== 2. Problem ==
17 +=== 3.2 Problem ===
16 16  
17 17  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.
18 18  
19 -== 3 Analysis ==
21 +=== 3.3 Analysis ===
20 20  
21 -=== 3.1 Errors in eMagiz ===
23 +==== 3.3.1 Errors in eMagiz ====
22 22  
23 23  We learned that calling the web service from a tool such as SOAP UI took a little over one minute when looking into an issue. This was the first signal to consider the option that because the call was taking over a minute, eMagiz shut down the connection before the call could be finished. This is because, on default, eMagiz holds a connection open for a maximum of one minute before closing the connection.
24 24  
... ... @@ -28,7 +28,7 @@
28 28  
29 29  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.
30 30  
31 -== 4. Result ==
33 +=== 3.4 Result ===
32 32  
33 33  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.
34 34