This documentation is for WSO2 Complex Event Processor 4.0.0. View documentation for the latest release.
WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.

Versions Compared

Key

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

...

In multitenant mode, the WSO2 Carbon runtime limits the thread execution time. That is, if a thread is stuck or taking a long time to process, Carbon detects 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
languagexml
<Valve className="org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve" threshold="600"/>

 

  • The className is the Java class used for the implementation. Set it to org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.
  • The threshold gives the minimum duration in seconds after which a thread is considered stuck. The default value is 600 seconds.

...

of . This   if you want to increase the throughput by receiving a higher number of events
PropertyDescriptionDefault ValueRecommendation
workerThreads The number of threads reserved to handle the load of events received.10This value should be increased if you want to increase the throughput by by receiving a higher number of events at a given time. The number of available CPU cores should be considered when specifying this value. If the value specified exceeds the number of CPU cores, higher latency would occur as a result of context switching taking place more often.eventBufferCapacity
maxEventBufferCapacityThe maximum size allowed for the event receiving buffer in mega bytes. The event receiving buffer temporarily stores the events received before they are forwarded to an event stream.1000010This value should be increased when there is an increase in the receiving throughput. When increasing the value heap memory size also needs to be increased accordingly.
eventBufferSizeThe number of messages that is allowed in the receiving queue at a given time.
PropertyDescriptionRecommendation
workerThreads

Number of threads in consumer to handle the load. Default value is 10.

Value should be higher when receiving throughput is high. Should to consider number of CPU cores.
eventBufferCapacitySize of the receiving event buffer. Default value is 10000.Needs to be higher value when receiving throughput is high. When increasing the value heap memory size also needs to be increased accordingly.  2000This value should be increased when there is an increase in the receiving throughput .
Publishing events

The following parameters which affect the performance relating to publishing events are configured in the <CEP_HOME>/repository/conf/data-bridge/data-agent-config.xml file. These configurations are common for both thrift and binary protocols.

...