Hi @joel30,

Normally, the Tunnel Stream will be closed once connection go down. There is no recovery on tunnel stream connection, so application has to create a new Tunnel Stream once the connection is recovered.

However, with current EMA version, 3.4.0, application may receive the 'Service not available', when it immediately re-create Tunnel Stream after the connection is recovered (Login Open/Ok received). This is because the service is not available immediately after the connection is recovered.

The current workaround is to register for Directory event to ensure that the service is immediately when the application tries to re-create Tunnel Stream.

Below are the summary instructions to recover the tunnel stream.
1. Application register for Login event to monitor connection and also register for Directory event to monitor when source directory become available.

LoginReq loginReq = EmaFactory.Domain.createLoginReq();consumer.registerClient(loginReq.message(), appClient);
ReqMsg reqMsg = EmaFactory.createReqMsg();consumer.registerClient(reqMsg.domainType(EmaRdm.MMT_DIRECTORY).serviceName("DDS_TRCE"), appClient);

2. Once Connection down, application will receive Login Status: Suspect/Open indicating that connection is down. Application will also receive System Status: Closed Recoverable/Suspect indicating that Tunnel Stream is closed.

----- Status message ----
StatusMsg
streamId="1"
domain="Login Domain"
state="Open / Suspect / None / ''"
StatusMsgEnd

----- Status message ----
StatusMsg
streamId="6"
domain="System Domain"
privateStream
state="Closed, Recoverable / Suspect / None / 'channel down.'"
name="TUNNEL1"
serviceId="10"
serviceName="DDS_TRCE"
StatusMsgEnd

3. EMA will automatically reconnect to the server. Once the connection is established, application will receive Login Refresh: Open/Ok indicating that connection is up.

----- Refresh message ----
RefreshMsg
streamId="1"
domain="Login Domain"
solicited
RefreshComplete
state="Open / Ok / None / ''"

    public void onRefreshMsg(RefreshMsg refreshMsg, OmmConsumerEvent event)    { 
        if(refreshMsg.domainType() == EmaRdm.MMT_LOGIN && refreshMsg.state().streamState() == OmmState.StreamState.OPEN && refreshMsg.state().dataState() == OmmState.DataState.OK)         {             
// Connect is up
connectionUp=true;         
}

4. After that, application needs to wait for Directory Update event received, and then re-create a new Tunnel Stream and continue posting data on the created Tunnel Stream.

    public void onUpdateMsg(UpdateMsg updateMsg, OmmConsumerEvent event)    {         if(updateMsg.domainType() == EmaRdm.MMT_DIRECTORY && connectionUp == true)         {             
           System.out.println("Starting tunnel stream...");             
           ClassOfService cos = EmaFactory.createClassOfService()....

Hello @joel30

Could you try EMA Consumer - Posting data to TR Contribution Channel tutorial source code? This is to verify if the server, service, your account credential, RICs are correct and ready or not.

• If you can post data using the tutorial source code, I suggest you reach out to the development team for further investigation for the application and EMA. You can submit your problem to the development team directly via Refinitiv/Elektron-SDK Github then click "New issue" button.
• If you cannot post data using the tutorial source code, please contact Refinitv account team to verify the server, service, your account credential and RICs.

@joel30

You may need to set logging to the FINEST level to see more information.

For example, create a new logging.properties file with this content.

#This file contains log configuration for java logging API.

# Level mapping between jdk and slf4j logging
# jdk.util.logging     SLF4J 
# FINEST              -> ALL
# FINEST               -> DEBUG
# FINEST               -> TRACE
# INFO                -> INFO
# WARNING             -> WARN
# SEVERE              -> ERROR

.level=FINEST
 
#handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler
handlers=java.util.logging.FileHandler

#java.util.logging.ConsoleHandler.level=FINEST
#java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
 
java.util.logging.FileHandler.level=FINEST
java.util.logging.FileHandler.pattern=./emaj.log
 
# Write 100000 bytes before rotating this file
java.util.logging.FileHandler.limit=50000000
 
# Number of rotating files to be used
java.util.logging.FileHandler.count=20
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
# Format timestamp as date/time with millisecond
#java.util.logging.SimpleFormatter.format=%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS.%1$tL %4$-7s %2$s %n%5$s

Then, run the application with the following VM argument.

-Djava.util.logging.config.file=logging.properties

The emaj.log file will be created.

For more information regarding logging, please refer to section Troubleshooting in this tutorial.

I have created an issue on Refinitiv Github handle regarding this. I tried with the sample ema consumer for posting data to TRCC plugging in our configuration and it worked fine.

@joel30

I found the following messages in the emaj.log file.

2020-02-19 11:21:02.153  INFO 317320 --- [pool-2-thread-1] c.bnc.refinitiv.client.RefinitivClient   : ----- Status message ----
2020-02-19 11:21:02.153  WARN 317320 --- [pool-2-thread-1] c.bnc.refinitiv.client.RefinitivClient   : Could not open tunnel stream expectedTunnelHandle=1, eventTunnelHandle=1, streamState=3
2020-02-19 11:21:02.153 TRACE 317320 --- [pool-2-thread-1] c.t.ema.access.OmmConsumerImpl           : loggerMsg
    ClientName: ItemCallbackClient
    Severity: Trace
    Text:    Removed Item 2 from item map
    Instance name BNC_Consumer_1
loggerMsgEnd


2020-02-19 11:21:02.153 TRACE 317320 --- [pool-2-thread-1] c.t.ema.access.OmmConsumerImpl           : loggerMsg
    ClientName: ItemCallbackClient
    Severity: Trace
    Text:    Removed Item 1 of StreamId 5 from item map
    Instance name BNC_Consumer_1
loggerMsgEnd

From the messages, the tunnel stream has been closed with streamState=3 (CLOSED_RECOVER). It may be closed due to disconnection. You can register for MMT_LOGIN to monitor the connection status or contact the server team to verify the server log for disconnections. To register to MMT_LOGIN, please refer to this thread.

Therefore, when the tunnel stream has been closed, the application needs to re-establish the tunnel stream before posting data.

I get the below error from the service logs:

StatusMsg

streamId="6"

domain="System Domain"

privateStream

state="Closed, Recoverable / Suspect / None / 'Service not available'"

name="BNC_Tunnel"

serviceId="10"

serviceName="DDS_TRCE"

StatusMsgEnd

Hello @joel30

Service not available may cause from the service goes down. Please contact Refinitiv account team who should help you to contact the server team to verify the service.