This documentation is for WSO2 Enterprise Integrator version 6.0.0 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.

All docs This doc
Skip to end of metadata
Go to start of metadata

Note that WSO2 EI is shipped with the following changes to what is mentioned in this documentation:

  • <PRODUCT_HOME>/repository/samples/ directory that includes all Integration profile samples is changed to <EI_HOME>/samples/service-bus/.
  • <PRODUCT_HOME>/repository/samples/resources/ directory that includes all artifacts related to the Integration profile samples is changed to <EI_HOME>/samples/service-bus/resources/.

Objective: Demonstrate the use of throttle mediator for concurrency throttling.

<definitions xmlns="">
    <sequence name="main">
            <throttle id="A">
                    <!-- define throttle policy -->
                    <wsp:Policy xmlns:wsp=""
                    <log level="custom">
                        <property name="text" value="**Access Accept**"/>
                            <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
                    <log level="custom">
                        <property name="text" value="**Access Denied**"/>
                        <code value="tns:Receiver"
                        <reason value="**Access Denied**"/>
                    <property name="RESPONSE" value="true"/>
                    <header name="To" action="remove"/>
            <throttle id="A"/>


  • Deploy the SimpleStockQuoteService in sample Axis2 server and start it on port 9000.
  • Start ESB with the sample configuration 370 (i.e. wso2ei-samples -sn 370).

Above configuration specifies a throttle mediator inside the in mediator. Therefore, all request messages directed to the main sequence will be subjected to throttling. Throttle mediator has 'policy', 'onAccept' and 'onReject' tags at top level. The 'policy' tag specifies the throttling policy for throttling messages. This sample policy only contains a component called "MaximumConcurrentAccess" .This indicates the maximum number of concurrent requests that can pass through Synapse on a single unit of time. To test concurrency throttling, it is required to send concurrent requests to Synapse. If Synapse with above configuration, receives 20 requests concurrently from clients, then approximately half of those will succeed while the others being throttled. The client command to try this is as follows.

ant stockquote -Dsymbol=IBM -Dmode=quote -Daddurl=http://localhost:8280/
  • No labels