We found the root cause is due to DN095602 change effective on 26th March, the RDMFieldDictionary and enumtype.def has been updated, which caused RFA API can't recieve NYMEX data correctly . After update the data dico file, the data issue was fixed.

Hello @Raj.Huang

Basically, the RFA API just receives an incoming data from the Provider/TREP infrastructure and passes it to the application as it is.

Could you please give us the RFA trace file when the problem occurs? It will let us verify if the EED sent those data to the API or not.

How to generate trace file? thanks.

Hi @Raj.Huang

You can configure the following RFA Java configurations to enable the log file

• <namespace>/Connections/<Connection Name>/ipcTraceFlags = 7
• <namespace>/ Connections/<Connection Name>/mountTrace = True
• <namespace>/ Connections/<Connection Name>/logFileName=<path to log file>

Please note that the application requires to restart to take the configurations changed effect.

Example:

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

Hi, if RDMFieldDictionary and enumtype.def has updates, how can client subscribe the update notificiaton? If we can't update timely , we may have big risk that API can't recieve data from EED and business will be down. thanks.