Troubleshooting Event Streaming Framework Log File Errors

Event streaming errors are logged in the Event Streaming Framework mtx_event_streamer.log file. You can use these errors to correct or work around problems with an event stream.

mtx_event_streaming.log Messages

The default Event Streaming Framework log file location is ${MTX_LOG_DIR}/mtx_event_streamer.log. If the Event Streaming Framework receives an error message back from the TRA-SI/DR, it converts it into an error like this one in the log file:

ERROR Got TRA error with result: 1001/Requested node 'id' is unreachable

For more information about the MATRIXX environment variables, see the discussion about installation directories, navigation shortcuts, and environment variables in MATRIXX Installation and Upgrade.

No Connector/Unrecoverable Error causes Event Streaming Framework Shutdown

Event Streaming Framework shuts down if you do not have a valid connector configured or if it encounters an unrecoverable connection error. In the case of no valid connectors, it returns this error message:

 com.matrixx.eventStreamer.util.NoConnectorException: No connector can be found

For details on creating streams and connectors, see the discussion about Event Streaming Framework properties and examples.

TRA-SI/DR Error Response Messages

These error messages are included in response messages that the TRA-SI/DR sends to the Event Streaming Framework.

mtx_event_streamer.log
When the request does not contain the correct TRA-SI/DR routing information, you will get an error message like this one:
```
Key: "Result"
Value: "1001"
Key: "ResultText"
Value: "TRA does not have requested 'id' in pool/node configuration"
```
This error is unrecoverable. This error is logged, and the Event Streaming Framework server shuts down so you can correct the error in the mtx_event_streamer.properties file and restart the Event Streaming Framework. For details about the property file, see the discussion about Event Streaming Framework properties.
When the target TRA-SI/DR node is unresponsive:
```
Key: "Result"
Value: "1002"

Key: "ResultText"
Value: "Requested node 'id' is unreachable" 
```
Retry the request. If you get more of these messages, diagnose the issue with the TRA-SI/DR node and then retry the request.
When the Event Streaming Framework has received too many requests at the same time:
```
Key: "Result"
Value: "1003"

Key: "ResultText"
Value: "Event Streaming proxy connection limit" 
```
Retry the request when fewer requests are running.