WSO2 ESB's Java Message Service (JMS) transport allows you to easily send and receive messages to queues and topics of any JMS service that implements the JMS specification. The following sections describe how you can tune the JMS transport of WSO2 ESB for better performance.
Increase the maximum number of JMS proxies
If you create several JMS proxy services in WSO2 ESB, you will see a message similar to the following:
WARN - JMSListener Polling tasks on destination : JMStoHTTPStockQuoteProxy18 of type queue for service JMStoHTTPStockQuoteProxy18 have not yet started after 3 seconds ..
This issue occurs when you do not have enough threads available to consume messages from JMS queues. The maximum number of concurrent consumers (that is, the number of JMS proxies) that can be deployed is limited by the base transport worker pool that is used by the JMS transport. You can configure the size of this worker pool using the system properties
lst_t_max. Note that increasing these values will also increase the memory consumption, because the worker pool will allocate more resources.
Similarly, you can configure the current number and the anticipated number of outbound JMS proxies using the system properties
To adjust the values of these properties, you can modify the server startup script if you want to increase the available threads for all transports (requires more memory), or create a
jms.properties file if you want to increase the available threads just for the JMS transport. Both approaches are described below.
To increase the threads for all transports
- Open the wso2server.sh or wso2server.bat file in your
<ESB_HOME>/bindirectory for editing.
- Change the values of the properties as follows:
To increase the threads for just the JMS transport
- Create a file named
jms.propertieswith the following properties:
- Create a directory called
<ESB_HOME>directory and save the file in this directory.
Configuring JMS Listener
You can increase the JMS listener performance by
Using concurrent consumers
Concurrent consumers is the minimum number of threads for message consuming. If there are more messages to be consumed while the running threads are busy, then additional threads are started until the total number of threads reaches the value of he maximum number of concurrent consumers (ie.,
MaxConcurrentConsumers). The maximum number of concurrent consumers (or the number of JMS proxies) that can be deployed is limited by the base transport worker pool that is used by the JMS transport. The size of this worker pool can be configured via the system property 'lst_t_core' and 'lst_t_max' as described above. The number of concurrent producers are generally limited by the Synapse core worker pool.
Concurrent consumers are only applicable to JMS queues not for JMS topics.
To increase the JMS listener performance
Add the following parameters to the JMS listener configuration of the
transport.jms.ConcurrentConsumers: the concurrent threads that need to be started to consume messages when polling.
transport.jms.MaxConcurrentConsumers: the maximum number of concurrent threads to use during polling.
The value for
locked attribute must be set to
false to create multiple listener threads. When this value is set to
true only one listener thread will be created at a given time.
Add the following parameter to the JMS listener configuration of the
<ESB_HOME>/repository/conf/axis2/axis2.xml file to enable caching:
The possible values for the cache level are
consumer. Out of the possible values,
consumer is the highest level that provides maximum performance.
After adding concurrency consumers and cache level, your complete configuration would be as follows:
Configuring JMS Sender
Add the following parameter to the JMS sender configuration of the
The possible values for the cache level are
producer. Out of the possible values,
producer is the highest level that provides maximum performance.
producer as the cache level, ensure to add the JMS destination parameter to avoid the following error:
INFO - AxisEngine [MessageContext: logID=2eabe85aeeb3bb62c26bb46d21b11b087ebf1e5e0b350839] JMSCC0029: A destination must be specified when sending from
ClientApiNonBlocking when sending messages via JMS
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 can be vital when queuing transports like JMS are involved.
To remove the
Add the following parameter to the configuration: