RFA client is not able to connect to data stream via LPC.

rokas.serepka

Hello,

We have Java RFA client which we are trying to connect to RTO via LPC (RFA -> LPC -> RTO).

Our RFA client is old but it is tested to work with direct connection. LPC has been installed on Linux server and it is tested to work with your test tool: testclient -s ELEKTRON_DD -u XXX etc...

When we are trying to connect with RFA client to LPC we get following errors:

1218-102727.346-I-(BaseReutersClient) - Sending login request. Username: XXX, appId: 256, ipAddress: localhost:14002.
1218-102731.308-I-(BaseReutersClient) - ... request sent
Dec 18, 2023 10:27:31 AM com.reuters.rfa.internal.session.ConnectionHandler createConnections
FINE: com.reuters.rfa.session._Default.RSSLSession
Session initialization: acquiring connection "_Default::RSSLconnection"

Dec 18, 2023 10:27:31 AM com.reuters.rfa.internal.connection.ConnectionImpl processConnectionStatusOpenReqMsg
FINE: com.reuters.rfa.connection.rssl._Default.RSSLconnection
Sending CONNECTION_STATUS_MSG, connection name = _Default::RSSLconnection, status = { state: DOWN, code: NONE, text: "uninitialized"}

Dec 18, 2023 10:27:36 AM com.reuters.rfa.internal.connection.ConnectionImpl processConnectionStatusBase
FINE: com.reuters.rfa.connection.rssl._Default.RSSLconnection
Sending CONNECTION_STATUS_MSG, connection name = _Default::RSSLconnection, status = { state: UP, code: NONE, text: ""}

1218-102736.185-W-(BaseReutersClient) - com.reuters.rfa.session._Default.RSSLSession
Login Response null does not match Login Request name XXX

Dec 18, 2023 10:27:36 AM com.reuters.rfa.internal.session.omm.OMMUserESHContext updateInternalStatesFromMsg
WARNING: com.reuters.rfa.session._Default.RSSLSession
Login Response null does not match Login Request name XXX

1218-102736.186-W-(BaseReutersClient) - com.reuters.rfa.session._Default.RSSLSession
Connection _Default::RSSLconnection does not support optimized Pause/Resume. Optimized Pause/Resume requests will be converted to individual item Pause/Resume requests for this connection.

Dec 18, 2023 10:27:36 AM com.reuters.rfa.internal.session.omm.OMMUserESHContext updateInternalStatesFromMsg
WARNING: com.reuters.rfa.session._Default.RSSLSession
this connection.lt::RSSLconnection does not support optimized Pause/Resume. Optimized Pause/Resume requests will be converted to individual item Pause/Resume requests for

1218-102736.186-W-(BaseReutersClient) - com.reuters.rfa.session._Default.RSSLSession
Connection _Default::RSSLconnection does not support Pause/Resume. Pause and Resume requests for this connection will be ignored.

Dec 18, 2023 10:27:36 AM com.reuters.rfa.internal.session.omm.OMMUserESHContext updateInternalStatesFromMsg
WARNING: com.reuters.rfa.session._Default.RSSLSession
Connection _Default::RSSLconnection does not support Pause/Resume. Pause and Resume requests for this connection will be ignored.

1218-102736.191-E-(BaseReutersClient) - com.reuters.rfa.connection.rssl._Default.RSSLconnection
Caught internal exception com.reuters.rfa.omm.OMMException: Invalid AttribInfo.
  com.reuters.rfa.internal.rwf.RwfMsgImpl.setAttribInfo(Unknown Source)
  com.reuters.rfa.internal.session.omm.OMMUserESHContext.encodeStatusMessage(Unknown Source)
  com.reuters.rfa.internal.session.omm.OMMUserESHContext.createAnInitialStatus(Unknown Source)
  com.reuters.rfa.internal.session.omm.OMMUserESHContext.handleAndAggregateLoginRespMsg(Unknown Source)

Dec 18, 2023 10:27:36 AM com.reuters.rfa.internal.connection.rssl.RSSLConnection processTransportData
SEVERE: com.reuters.rfa.connection.rssl._Default.RSSLconnection
Caught internal exception com.reuters.rfa.omm.OMMException: Invalid AttribInfo.
  com.reuters.rfa.internal.rwf.RwfMsgImpl.setAttribInfo(Unknown Source)
  com.reuters.rfa.internal.session.omm.OMMUserESHContext.encodeStatusMessage(Unknown Source)
  com.reuters.rfa.internal.session.omm.OMMUserESHContext.createAnInitialStatus(Unknown Source)
  com.reuters.rfa.internal.session.omm.OMMUserESHContext.handleAndAggregateLoginRespMsg(Unknown Source)

Username was taken from LPC user_list.txt. Variables (Username: XXX, appId: 256, ipAddress: localhost:14002) are provided from our configuration and set in login message.

Our RSSLconnection configuration:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE preferences SYSTEM ">http://java.sun.com/dtd/preferences.dtd&gt;
<preferences EXTERNAL_XML_VERSION="1.0">
    <root type="user">
        <map/>
        <node name="com">
            <map/>
            <node name="reuters">
                <map/>
                <node name="rfa">
                    <map/>
                    <node name="_Default">
                        <map/>
                        <node name="Connections">
                            <map/>
                            <node name="RSSLconnection">
                                <map>
                                    <entry key="connectionType" value="RSSL"/>
                                    <entry key="serverList" value="localhost"/>
                                </map>
                            </node>
                        </node>
                        <node name="Sessions">
                            <map/>
                            <node name="RSSLSession">
                                <map>
                                    <entry key="connectionList" value="_Default::RSSLconnection"/>
                                </map>
                            </node>
                        </node>
                    </node>
                </node>
            </node>
        </node>
    </root>
</preferences>

Could you please help as out with the problem above?

Jirapongse

@rokas.serepka

Thank you for reaching out to us.

It could be a bug in the API.

RFAJAVA-511; Consumer application fails when the Login Response has
attribute information, but has none defined.
This has been fixed.

It has been fixed in rfaj8.0.0.E2.all.

Please check the version of RFA Java that you are using.

wasin.w

Hello @rokas.serepka

If the problem still persisting with the rfaj8.0.0.E2.all (and above), please enable the RFA trace file when the problem occurs and share the file on this post.

### Example RFA Java Configurations for the trace file ###

<node name="rsslConnection">
   <map>
      <entry key="connectionType" value="RSSL"/>
      <entry key="serverList" value="localhost"/>
      <entry key="portNumber" value="14002"/>
      <entry key="ipcTraceFlags" value="7"/>
      <entry key="mountTrace" value="True"/>
      <entry key="logFileName" value=".\logs\RSSL_%U.log"/>
   </map>
</node>

rokas.serepka

The dependency we do have is:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.8.2
Created-By: 1.6.0_25-b06 (Sun Microsystems Inc.)
Build-Date: 2012-05-31 11:42:16
Specification-Title: RFA Java
Specification-Version: 7.2.1
Specification-Vendor: Thomson Reuters
Package-Version: 7.2.1.L1.all
Implementation-Version: 7.2.1.L1.all

How do we go about updating it? Does this require code change or just replacing jar file in classpath?

Jirapongse

@rokas.serepka

For RFA Java 7.x, this issue has been fixed in RFA Java 7.6.1.

The latest version of RFA Java 7.x is 7.8.1.L1. Please use RFA Java 7.8.1.L1 instead.

Typically, you can set the classpath to the latest RFA Java. However, please make sure that the old jar files aren't loaded.

You can download RFA Java from the Software Downloas on MyRefinitiv. It is in Product Family: MDS - API and Product: Robust Foundation API (RFA) - Java.

rokas.serepka

https://community.developers.refinitiv.com/discussion/comment/112493#Comment_112493

Updating FRA API worked. Thank you!