Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

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

...

Exception
Code Block
event for endpoint group [ ( Receiver URL : tcp://das-1.amway-prod.local:7611, Authentication URL : ssl://das-1.amway-prod.local:7711),( Receiver URL : tcp://das-2.amway-prod.local:7611, Authentication URL : ssl://das-2.amway-prod.local:7711) ], 139882 events dropped so far. {org.wso2.carbon.databridge.agent.DataPublisher}
TID: [-1] [] [2017-05-23 00:05:53,708] ERROR
{org.wso2.carbon.databridge.agent.endpoint.DataEndpoint} - Unable to send events to the endpoint. {org.wso2.carbon.databridge.agent.endpoint.DataEndpoint}
org.wso2.carbon.databridge.agent.exception.DataEndpointException: Cannot send Events
Possible reasons
  • The TCP connection between the databridge client and the DAS server may not be established.
  • The performance of WSO2 DAS may not be tuned to handle the event load sent by the databridge client.
  • If the database is an RDBMS database such as MySQL, this exception can occur due to limited capacity.
Troubleshooting options

To check the TCP connection, enable event tracing and event logs, and make sure that one or more events are published to WSO2 DAS.
To enable event tracing, see Event Tracer.
To enable event logging, see Logger Event Publisher.

Recommended action
  • To check the database persistence and database receiver rate, the following properties can be set when the DAS server is started:
    • -DprofileReceiver=true: Setting this property when starting the DAS server This enables you to check the throughput per receiver. This creates the receiver-perf.txt file in the DAS_HOME. The throughput is calculated and published in this file for every 100000 events.
    If the database is an RDBMS,
    • -DprofilePersistence=true: This allows you to check the throughput at the persistence (i.e., Data Access Layer) level. This creates the persistence-perf.txt file in the DAS_HOME.
    • -DpersistenceStatsCutoff=1000: This property specifies the number of events for which the persistence-perf.txt file generated via the -DprofilePersistence property is updated. If this property is not set, 100000 is considered the default number.
  • NoSQL databases such as HBase are recommended for high throughput environments to avoid this exception.