question

Upvotes
Accepted
11 4 4 8

Missing some fields after upgraded to EMA RTSDK 2.0.2.L1 Java

Missing some fields after upgraded to EMA RTSDK 2.0.2.L1 Java from ESDK 1.0.0 after client migrated to RTO LPC.


Any way to fix it? Please see attached snap shot Before and After

elektronelektron-sdkrrtrefinitiv-real-time
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

@Hao.Tang

Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If so please can you click the 'Accept' text next to the appropriate reply? This will guide all community members who have a similar question or could you provide the information required for further investigation, please?

Thanks,
AHS


Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.

Thanks,


AHS



Upvotes
Accepted
25.3k 87 12 25

Hi @Hao.Tang

Changing SDK or upgrading versions should not affect the list of fields received.

The SDK will pass on whatever payload it receives from the server - it does not change or amend the payload.

The customer should try running the old and new code side by side to confirm this.

One thing to note, if they have changed from EC to RTO - then the number of updates they receive may be different - as EC and RTO may not use the same bandwidth optimisation/conflation mechanism.

If they still see differences in data, then the RTO team would have to investigate any such data differences.


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Hi @Hao.Tang and @umer.nalla ,

Just a quick verification, the customer is connecting to RTO directly with EMA Java, and is not via LPC, as in question, which would be redundant.

Upvotes
11 4 4 8

before.jpg (71.2 KiB)
after.jpg (52.7 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
58 2 0 2

客户您好!漏掉的字段有可能是因为没有订阅这些字段,您可以请客户检查一下升级SDK后的代码是否订阅了所有需要的字段(fields),如果没有可以请客户订阅(subscribe)所有所需字段之后再试一下。谢谢!

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

客户在升级SDK过程中并没有在原有程序做任何变更,请问丢失字段是SDK升级的必然现象吗?客户想了解具体的原因

Hi @umer.nalla , Yu has no idea about this question, do you have any helpful info about this? Thanks in advance!


Translated it into English, "The customer did not make any changes to the original program during the SDK upgrade process. Is the missing field an inevitable phenomenon of the SDK upgrade? The customer wants to understand the specific reason "

1)如Umer所确认,升级SDK不会影响之前订阅的字段,现在更新频率没变化,只是字段有丢失,请问这是什么原因?

2) 客户还提到有内存泄露问题,之前建议升级最新RTSDK 2.0.2,但升级之后仍然存在同样问题,可不可以帮忙看看分析一下原因(附件)498501245.jpg

021-09-26T10:44:06.449+0800: 315081.259: [GC cleanup 3737M->3737M(4096M), 0.0052791 secs]
 [Times: user=0.07 sys=0.00, real=0.00 secs] 
@汤浩 然后这边看一下,升级sdk后内存泄漏问题还是没有解决
498501245.jpg (195.2 KiB)

Hi @Hao.Tang

As mentioned earlier if they are running old and new applications side by side and can confirm data is missing from the new feed, you will need to ask the RTO team to investigate.

We on the Dev Forum do not have the ability to investigate missing data/content issues. Please raise a Ticket for the Real-Time Optimized service and the client will need to provide details of the differences i.e. times and fields which are seen with the old feed and not the new feed.

In terms of the memory leak issue, the forum is not the ideal scenario for this - as it would require deeper investigation by RDC + the dev team and would require much more information from the customer than just the call stack attached above.

To Contact RDC you can raise a premium support ticket from Refinitiv Real-Time Java SDK | Refinitiv Developers :

Or they can report directly to the Dev Team at Issues · Refinitiv/Real-Time-SDK (github.com) Issues · Refinitiv/Real-Time-SDK (github.com)

hi @Hao.Tang

Apologies but I should have been clearer in the above post. You need to work with RDC to recreate and confirm there is a memory leak in EMA before reporting it on GitHub. The EMA dev team are not in a position to help diagnose a possible memory leak in an application.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.