Troubleshooting Event Publishers

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(DataEndpointGroup.java:124) at org.wso2.carbon.databridge.agent.endpoint.DataEndpointGroup$EventQueue.access$100(DataEndpointGroup.java:104) at org.wso2.carbon.databridge.agent.endpoint.DataEndpointGroup.tryResendEvents(DataEndpointGroup.java:295) at org.wso2.carbon.databridge.agent.endpoint.DataEndpoint$EventPublisher.handleFailedEvents(DataEndpoint.java:271) at org.wso2.carbon.databridge.agent.endpoint.DataEndpoint$EventPublisher.run(DataEndpoint.java:245) at java.lang.Thread.run(Thread.java:745) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: com.lmax.disruptor.InsufficientCapacityException
Occurrence	This occurs when events published by WSO2 DAS 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. This is done by editing the `QueueSize` parameter in the `<DAS_HOME>/repository/conf/data-bridge/data-agent-config.xml` file. Use a non-blocking WSO2 event publisher. For more information on how to configure a non-bloking data publisher, see Publishing Data Using Java Client Through Thrift or Binary - Data Publisher Sample .