WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.
Skip to end of metadata
Go to start of metadata

The possible exceptions relating to event publishers that may occur are as follows:

Unable to accept requests from event receivers (WSO2 event publisher)

Sample Error log
org.wso2.carbon.databridge.agent.exception.EventQueueFullException: Cannot send events because the event queue is full
at org.wso2.carbon.databridge.agent.endpoint.DataEndpointGroup$EventQueue.tryPut(
at org.wso2.carbon.databridge.agent.endpoint.DataEndpointGroup$EventQueue.access$100(
at org.wso2.carbon.databridge.agent.endpoint.DataEndpointGroup.tryResendEvents(
at org.wso2.carbon.databridge.agent.endpoint.DataEndpoint$EventPublisher.handleFailedEvents(
at org.wso2.carbon.databridge.agent.endpoint.DataEndpoint$
at java.util.concurrent.Executors$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: com.lmax.disruptor.InsufficientCapacityException
OccurrenceThis occurs when events published by WSO2 CEP do not reach the endpoint.
Possible reasons
  • A failure in the network connection.
  • Unavailability of the receiver node to which the events are published (e.g., if it is unreachable, shut down etc.)
  • The internal queue of the recover node to which the events are published being full.
Recommended action
  • Increase the event queue size at databridge level.
  • Use a non-blocking WSO2 event publisher.
  • No labels