This documentation is for WSO2 Data Services Server 3.2.2. View documentation for the latest release.
Page Comparison - Performance Tuning (v.16 vs v.17) - Data Services Server 3.2.2 - WSO2 Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

When it comes to web applications, users are free to experiment and package their own pooling framework such BoneCP.

Setting the thread execution limit for multi-tenant mode

In multi-tenant mode, the Carbon runtime limits the thread execution time. That is, if a thread is stuck or taking a long time to process, Carbon will detect such threads, interrupts and stops them. Note that Carbon prints the current stack trace before interrupting the thread. This mechanism is implemented as an Apache Tomcat valve. Therefore, it should be configured in the <PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml file as shown below.

Code Block
<Valve className="org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve" threshold="600"/>
  • The className is the Java class name used for the implementation. This must be set to org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.
  • The threshold gives the minimum duration in seconds after which a thread is considered stuck. Default value is 600 seconds.

Other tips

When you need high update/insert throughput, use batch requests to achieve maximum performance. Batch requests send multiple records in a single request. For more information on batch processing, see Batch Processing Sample.