Page Comparison

This section provides information on how to improve the performance of the following most common JMS use cases of WSO2 Enterprise Integrator(WSO2 EI). 

Anchor
consumer consumer

WSO2 EI as a JMS consumer

In this scenario, WSO2 EI listens to a JMS queue, consumes messages, and sends the messages to a HTTP back-end service.

...

• If the queue gets filled up at a high rate, and the queue is long, you can improve the performance by increasing the number of concurrent consumers. Add the following parameters to the JMS listener configuration of the  <EI_HOME>/conf/axis2/axis2.xml file to increasing the number of concurrent consumers:
  

  Code Block
  language xml
  <parameter name="transport.jms.ConcurrentConsumers" locked="false">50</parameter> <parameter name="transport.jms.MaxConcurrentConsumers" locked="false">50</parameter>

• Add the following parameter to the JMS listener configuration of the  <EI_HOME>/conf/axis2/axis2.xml file to enable JMS listener caching:
  

  Code Block
  language xml
  <parameter name="transport.jms.CacheLevel">consumer</parameter>

  The possible values for the cache level are none, auto, connection, session and consumer. Out of the possible values, consumer is the highest level that provides maximum performance. 

Anchor
producer producer

WSO2 EI as a JMS Producer

...

In this scenario, a proxy service in WSO2 EI accepts messages from an HTTP client via HTTP and sends the messages to a JMS queue. 

...

• Add the following parameter to the JMS sender configuration of the  <EI_HOME>/conf/axis2/axis2.xml file to enable JMS sender caching:
  

  Code Block
  language xml
  <parameter name="transport.jms.CacheLevel">producer</parameter>

  The possible values for the cache level are none, auto, connection, session and producer. Out of the possible values, producer is the highest level that provides maximum performance.

• Add the following parameter to the configuration to remove ClientApiNonBlocking when sending messages via JMS:

  Code Block
  language xml
  <property name="ClientApiNonBlocking" action="remove" scope="axis2"/>

  Info
  title Noe
  By default, Axis2 spawns a new thread to handle each outgoing message. To change this behavior, you need to remove the ClientApiNonBlocking property from the message. Removal of this property is vital when queuing transports like JMS are involved.

...