Table of Contents


  1. Preface
  2. Introduction to Informatica Edge Data Streaming
  3. Licenses
  4. Using Informatica Administrator
  5. Creating and Managing the Edge Data Streaming Service
  6. Edge Data Streaming Entity Types
  7. Edge Data Streaming Nodes
  8. Data Connections
  9. Working With Data Flows
  10. Managing the Edge Data Streaming Components
  11. Security
  12. High Availability
  13. Disaster Recovery
  14. Monitoring Edge Data Streaming Entities
  15. Troubleshooting
  16. Frequently Asked Questions
  17. Regular Expressions
  18. Command Line Program
  19. Configuring Edge Data Streaming to Work With a ZooKeeper Observer
  20. Glossary

User Guide

User Guide

Troubleshooting Data Flows

The data flows do not appear correctly in the Administrator tool.
This error might occur if you have updated the Enterprise license to a Free license, and the EDS Node name is not the same as the host name. A license error occurs in the <EDS installation folder>/node/logs/<node name>-node.log file. When you start the EDS Node, use the host name as the EDS Node name.
The data flows are deployed, but the target services do not receive any data.
This error might occur if the network interfaces are not configured correctly. A no interfaces matching criteria exception occurs in the <EDS installation folder>/node/logs/<node name>-node.log file. Configure the correct interface in the networkInterface property in the <EDS installation folder>/node/config/node.cnf file.
The data flows are deployed, the source services and the target services are running but the target services do not receive any data.
This error might occur if the data flow uses UM Secure connection type in the data connection and the security related fields are not configured correctly. The EDS Node logs a security related error in the EDS Node log file. Specify correct values for the security related fields for the data connection and redeploy the data flows.
When I deploy a data flow, not all messages in the data flow are sent.
This error might occur if the machine on which the EDS Node is running is low on memory. An OutOfMemoryError: Direct buffer memory error occurs in the <EDS installation folder>/node/logs/<node name>-node.log file. Increase the system memory or free up some memory by closing applications that are occupying more memory before you deploy the data flow.
In a deployed data flow, there is discrepancy in the bytes sent and bytes received.
This discrepancy in statistics might occur if you restart the source EDS Node associated with the data flow when the data flow is deployed. When you stop and start the EDS Node, the statistics are not reported for the interval during which the EDS Node is down.
The data flows are deployed but there is a discrepancy in the data that is sent and received.
This discrepancy might occur in case of database or ZooKeeper corruption. The data flows that you create and deploy using the corrupt data might be in inconsistent states or contain stale data. In this case, recover the data manually. As the data flows are not automatically refreshed, you must manually recover them.
To recover the states of the data flows, perform the following tasks:
  1. Undeploy all data flows. To clear the ZooKeeper configuration or corrupted data from the data flows, perform a force clean when you undeploy all data flows.
  2. Deploy all data flows.
I am using a Syslog UDS source in the data flow and unable to log in to the machine on which the node is installed.
This issue might occur if the Syslog UDS source has stopped publishing messages after the target service turns inactive.
To resolve this issue, undeploy the data flow and change the messaging mode from load balancing to streaming.
I have configured a WebSocket data connection to connect to an external load balancer. I see that the source service is not sending data to the load balancer and I get the following error message in the EDS Node log file for the source services:
java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method)
This issue occurs if all the machines hosting the EDS Nodes for the target services are down.
To resolve this issue, perform the following steps:
  1. If deployed, undeploy the data flow.
  2. Start the EDS Nodes on the machines for the target services.
  3. Deploy the data flow.
When I deploy a data flow that has multiple sources and targets and that uses an Ultra Messaging data connection, I get the following error:
ERROR [src1-104] com.informatica.vds.reader.SourceWrapper - Exception in source
com.latencybusters.lbm.LBMEOPException: CoreApi-5688-3230: could not find open TCP server port 
in range [14371-14390]
This issue might occur because of the configuration of the Ultra Messaging connection.
To resolve this issue, specify the following configuration for the Ultra Messaging connection and deploy the data flow again:
<template name="entity-user-template">
<options type="context">
<option name="transport_tcp_port_high" default-value="30000"/>
<option name="transport_tcp_port_low" default-value="29000"/>

Updated March 19, 2019

Explore Informatica Network