Skip to Content
Last modified by Erik Bakker on 2024/09/03 10:48
From 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"
To version 18.1
edited by Erik Bakker
on 2024/09/03 10:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,26 +1,19 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -= Timeout occurred on a web service call =
3 -
4 4  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.
5 5  
6 6  Should you have any questions, please get in touch with academy@emagiz.com.
7 7  
8 -* Last update: March 8th, 2022
9 -* Required reading time: 3 minutes
6 +== 1. Situation ==
10 10  
11 -== 3. Timeout occurred on a web service call ==
12 -
13 -=== 3.1 Situation ===
14 -
15 15  At some point, questions were raised that the connection between eMagiz and an external SOAP web service ran into timeouts.
16 16  
17 -=== 3.2 Problem ===
10 +== 2. Problem ==
18 18  
19 19  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.
20 20  
21 -=== 3.3 Analysis ===
14 +== 3 Analysis ==
22 22  
23 -==== 3.3.1 Errors in eMagiz ====
16 +=== 3.1 Errors in eMagiz ===
24 24  
25 25  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.
26 26  
... ... @@ -30,8 +30,18 @@
30 30  
31 31  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.
32 32  
33 -=== 3.4 Result ===
26 +== 4. Result ==
34 34  
35 35  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.
36 36  
30 +== 5. Suggested Additional Readings ==
31 +
32 +* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
33 +** [[SOAP Web service connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.SOAP Web service Connectivity.WebHome||target="blank"]]
34 +*** [[Properties (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
35 +* [[RCA Knowledge Base (Menu)>>doc:Main.eMagiz Support.RCA Knowledge Base.WebHome||target="blank"]]
36 +** [[Configuration Issues (Navigation)>>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-configuration-issues.WebHome||target="blank"]]
37 +*** [[Incorrect flow configuration (Explanation)>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-configuration-issues.rca-knowledgebase-incorrect-flow-configuration.WebHome||target="blank"]]
38 +* [[Timeout Configuration (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22timeout+configuration%22||target="blank"]]
39 +
37 37  )))((({{toc/}}))){{/container}}{{/container}}