A client is using the latest EMA Java 2.0.1 connecting to RTO with a streaming request. They are experiencing the following behavior/error message:
We monitored another couple times of the behavior.
one time it stopped refresh rates after 18 minutes of working.
Another time it stopped refresh rates after 10 minutes.
Both reported the following error messages.
Item Name: ZMW=
Service Name: ELEKTRON_DD Item State: Open / Suspect / None / 'channel down.' Jul 07, 2021 11:33:59 AM com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallback INFO: loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_4 Instance Name Consumer_4_1 Component Version ads3.4.2.L1.linux.tis.rrg 64-bit loggerMsgEnd Jul 07, 2021 11:33:59 AM com.refinitiv.ema.access.LoginCallbackClient rdmLoginMsgCallback SEVERE: loggerMsg ClientName: LoginCallbackClient Severity: Error Text: RDMLogin stream was closed with status message username usernameType 5 State: Closed/Suspect/Application is denied access to the system - text: "TREP authentication failed (1026, Request for token validation failed:Authentication server did not contain "active" in response)." loggerMsgEnd
To verify the problem, the client may need to enable tracing in EMA. We need to enable tracing in both REST and RSSL connections.
1. Create the logging.properties file with the following content in the working directory
.level=ALL handlers=java.util.logging.FileHandler java.util.logging.FileHandler.level=ALL java.util.logging.FileHandler.pattern=./emaj%u.log
2. Add the XmlTraceToStdout configuration to the Consumer in the EmaConfig.xml. The following example adds the XmlTraceToStdout configuration to the Consumer_4 which is used to connect to RTO.
<Consumer> <Name value="Consumer_4"/> <Channel value="Channel_4"/> <Dictionary value="Dictionary_2"/> <XmlTraceToStdout value="1"/> </Consumer>
3. Run the application with the following JVM option
The interactions for the REST connection are logged in the emaxxx.log file and the interactions for the RSSL connection are printed to the standard output.
With this information, we can verify if it is a problem with the API or the server.