Skip to main content

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request.

CLIENT->WSO2 ESB->BACKEND

The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties.

1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB.

synapse.global_timeout_interval=120000


2) Socket timeout defined in the passthru-http.properties (ESB_HOME\repository\conf\) file. This parameter will decide on the timeout which a particular http request is waiting for a response. If ESB does not receive any response from the Back End during this period, HTTP connection get timed out and that will eventually throws timeout error in the ESB side and fault handlers will be hit.

http.socket.timeout=60000

3) You can define timeouts on the endpoint configuration such that it will affect only that particular endpoint. This will be a better option if you need to configure timeouts per endpoint for different Back End services. You can also define the action upon the timeout. Below example configuration will set the endpoint to timeout in 30 seconds and then execute the fault handler.

                  <timeout>
                     <duration>10000</duration>
                     <responseAction>fault</responseAction>
                  </timeout>

Comments

  1. When shopping for a Wedding loan, it’s important to consider the interest rate. This will be the primary factor in determining how much you pay for your loan. You can compare interest rates on online lenders to find the lowest possible rate.
    Loan For Wedding

    ReplyDelete
  2. The answer should be based on the complexity of your case, the results you are looking for, and other factors that could affect your outcome. You should also ask how the attorney prioritizes their work, including how they will allocate their time between different clients.
    Ohio Truck accident lawyer
    Massachusetts Lawyer Online
    Florida Lawyer Online

    ReplyDelete
  3. It is also helpful to understand how insurance works and the complexities of the policy language used.
    New York Commercial Truck Insurance
    Liberty Mutual demands $600,000 after cargo vanishes
    New risk management challenges in privacy class actions
    Commercial insurance is a contract between you and the insurer, whereby you pay a premium in exchange for the insurer’s promise to reimburse you in the event of a covered loss or liability.

    ReplyDelete
  4. It can also be more sophisticated, with apps that offer features like automatic syncing, debt payoff tracking and budgeting tools. The key is to find a tool that works for your needs and financial management style.
    Affordable Food Truck Loan

    Personal Loans in USA Company

    Best usa financial services

    ReplyDelete

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...

WSO2 ESB usage of get-property function

What are Properties? WSO2 has a huge set of mediators but property mediator is mostly used mediator for writing any proxy service or API. Property mediator is used to store any value or xml fragment temporarily during life cycle of a thread for any service or API. We can compare “Property” mediator with “Variable” in any other traditional programming languages (Like: C, C++, Java, .Net etc). There are few properties those are used/maintained by ESB itself and on the other hand few properties can be defined by users (programmers). In other words, we can say that properties can be define in below 2 categories: ESB Defined Properties User Defined Properties. These properties can be stored/defined in different scopes, like: Transport Synapse or Default Axis2 Registry System Operation Generally, these properties are read by get-properties() function. This function can be invoked with below 2 variations. get-property(String propertyName) get-property(String scop...