This documentation is for WSO2 Carbon 4.4.0. View documentation for the latest release.
Page Comparison - Performance Tuning (v.2 vs v.3) - Carbon 4.4.0 - WSO2 Documentation
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.

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 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 detects 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 Value 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 The className is the Java class name of used for the implementation. This must be set to to org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.
  • The The threshold gives the minimum duration in seconds after which a thread is considered stuck. Default value is 600 seconds.