For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
sudden close - channel down
I am facing a problem with the java application ( I used one of the examples listed in the files), the error message is shown in the attached file .
The application shuts down as it appears to be killed , this happens in random time order and not after specific duration or action.
Hello @H.H.
To be able to continue investing the problem, please
- attach EMA xml trace
- what is the EMA example application?
Hello @H.H.
Please set XmlTraceToStdout Consumer entry parameter to 1 in EmaConfig.xml located in the application’s run directory. For example:
<Consumer>
<Name value="Consumer_1"/>
...
<XmlTraceToStdout value="1"/>
</Consumer>
Then, EMA traces its received and sent messages in XML format to stdout/console. The xml trace log can be long so please redirect your application command output to a file as the syntax below:
Java_command_line_running_application > output_file_name
Hello @H.H.
Does the problem still occur? If so, please send me the following required info:
Hello @H.H.
Thanks for helpful info. According to the log file, I found that there was no error about LOGIN, SOURCE, DICTIONARY and MARKET_PRICE stream. All streams could open successfully and the application got data. However, in the end of log it showed:
<CLOSE domainType="LOGIN" streamId="1" containerType="NO_DATA" flags="0x00" dataSize="0">
<CLOSE domainType="SOURCE" streamId="2" containerType="NO_DATA" flags="0x00" dataSize="0">
The log messages can be generated when method uninitialize() method of OmmConsumer class is called. The method closes login and source stream while uninitializing OmmConsumer.
Does your application call uninitialize() method of OmmConsumer? In the example example100__MarketPrice__Streaming consumer.uninitialize() is called before the application exists. It is possible that you see the close message because the application calls the method.
In addition, I did not see "channel down" message in the given log. It seemed that your application and EMA worked properly.
Moreover, I strongly suggest you upgrade to the latest EMA Java shipped with
The latest EMA containing all latest fixes and it provides the log of connection process. For example:
<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/10.42.61.169:52601 remote=/192.168.27.48:14002] -->
<!-- Mon Jul 03 15:16:30 ICT 2017 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<CLOSE domainType="LOGIN" streamId="1" containerType="NO_DATA" flags="0x00" dataSize="0">
<dataBody>
</dataBody>
</CLOSE>
If there is any connection problem, we should be able to investigate it from the log.
We implemented the changes recommended , Its been running now without any issues.
The log messages can be generated when method uninitialize() method of OmmConsumer class is called. The method closes login and source stream while uninitializing OmmConsumer. Does your application call uninitialize() method of OmmConsumer? In the example example100__MarketPrice__Streaming consumer.uninitialize() is called before the application exists. It is possible that you see the close message because the application calls the method.
Thanks for the support