Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
This documentation is for WSO2 Message Broker version 3.2.0. For the latest documentation, see the documentation for WSO2 Enterprise Integrator.
Skip to end of metadata
Go to start of metadata

This section explains how to tune the performance of the WSO2 MB in terms of deployment in a clustered environment.

Improvement areaParameterDescriptionLocationDefault/Recommended Value
-Xms256m -Xmx1024m -XX:MaxPermSize=256m
The memory allocated for the WSO2 MB.

For Windows: <MB_HOME>/bin/wso2server.bat file

For Linux: <MB_HOME>/bin/wso2server.sh file

Generally, at least 2 GB memory is recommended for production instances.
Cluster healthhazelcast.max.no.heartbeat.seconds

The maximum time period that should elapse between pings received from a worker node in an MB cluster before acknowledging that worker node to be dead. This value is specified in seconds.

This parameter prevents the allocation of resources to inactive worker nodes, thereby avoiding unnecessary system overheads.

A short time duration can be specified in environments with a very high message flow and it is important to reallocate resources from inactive nodes to active nodes fast. A longer time duration can be specified in environments with lower message flows.

<MB_HOME>/repository/conf/hazlecast.properties file600
Cluster RecoveryconcurrentStorageQueueReadsThe number of storage queue reads carried out concurrently at a given time. This number should be set based on the number of storage queues that currently exist.<MB_HOME>/repository/conf/broker.xml file5
  • No labels