EIKON .NET API: Stub destroyed due to usage count = 0

PBI
PBI
in Eikon COM

Hi,

i use EIKON .NET API for real-time data subscriptions. My application launch 3 real-time data subscriptions and those subscriptions running as long as my application is running (from 9am to 5pm).

After some minutes/hours, i encounter an internal API error which is a something like a quota limitation usage. This is the API log when the error occurred:

2017/07/25 10:14:21:677 [TRACE] ThomsonReuters.Eikon.Ipc.StubBase - Ref count -- for stub 48561a12-d629-465b-9745-9837942b98f5IRawUdapServiceCallback. Total is now 0
2017/07/25 10:14:21:677 [INFO]  ThomsonReuters.Eikon.Ipc.ManagedInfra.StubManager - Stub destroyed due to usage count = 0 (StudbId=48561a12-d629-465b-9745-9837942b98f5IRawUdapServiceCallback)
2017/07/25 10:14:21:677 [DEBUG] ThomsonReuters.Eikon.Ipc.StubBase - Dispose(True) (StubId=48561a12-d629-465b-9745-9837942b98f5IRawUdapServiceCallback)
2017/07/25 10:14:21:677 [DEBUG] ThomsonReuters.Eikon.Ipc.ProxyStubBase - Dispose(True) (StubId=48561a12-d629-465b-9745-9837942b98f5IRawUdapServiceCallback)
2017/07/25 10:14:21:689 [WARN]  ThomsonReuters.Eikon.Ipc.RawRealtimeServiceProxyImpl - An error occured during RawRealtimeServiceProxyImpl.Subscribe() method invocation but the associated TaskCompletionSource was not found.
2017/07/25 10:14:21:960 [WARN]  ThomsonReuters.Eikon.Ipc.RawRealtimeServiceProxyImpl - An error occured during RawRealtimeServiceProxyImpl.Subscribe() method invocation but the associated TaskCompletionSource was not found.
2017/07/25 10:14:22:008 [WARN]  ThomsonReuters.Eikon.Ipc.RawRealtimeServiceProxyImpl - An error occured during RawRealtimeServiceProxyImpl.Subscribe() method invocation but the associated TaskCompletionSource was not found.
2017/07/25 10:14:22:056 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - Subscribe fails - Error:The operation has timed out.
2017/07/25 10:14:22:057 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - An error occured while starting data subscription.
System.TimeoutException: The operation has timed out.
2017/07/25 10:14:22:058 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - Subscribe fails - Error:The operation has timed out.
2017/07/25 10:14:22:078 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - An error occured while starting data subscription.
System.TimeoutException: The operation has timed out.
2017/07/25 10:14:22:078 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - Subscribe fails - Error:The operation has timed out.
2017/07/25 10:14:22:078 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - An error occured while starting data subscription.

For information:

- My application is running on 2 to 4 workstations and was shipped on our production environment on the 4th of July

-This errors appeared the first time the 12th of July at 2:54 (pm) and occur every day at 10:00 - 11:00 (am)

-Restarting the application make the subscriptions work again.

-When this error occur, if i start programmatically a new data subscription this error appear:

2017/07/25 11:01:54:690 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - Subscribe fails - Error:The operation has timed out.
2017/07/25 11:01:54:690 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - An error occured while starting data subscription.
System.TimeoutException: The operation has timed out.
2017/07/25 11:01:56:285 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - Subscribe fails - Error:The operation has timed out.
2017/07/25 11:01:56:285 [ERROR] ThomsonReuters.Desktop.SDK.DataAccess.Realtime.Impl.DataRequestBase - An error occured while starting data subscription.
System.TimeoutException: The operation has timed out.

Any help would be appreciated

Regards,

Pierre

Tagged:

Best Answer

  • pierre.faurel
    pierre.faurel
    Answer ✓

    Hi,

    It's difficult to identify a root cause, it needs a deep investigation.

    Could you contact the Eikon support (with Help \ Contact Us menu in Eikon Toolbar) ?

    Attach a zip archive that contains all log files from C:\ProgramData\Thomson Reuters\Eikon Data\Logs\TRD\<your session>\),

    and specify that the problem should be addressed to the Eikon Desktop SDK team.

    In addition, when you reproduce the issue, you can upload log files to the support : open the Log Viewer windows (Help \ Event Logs menu), then click on upload icon :

    image

    Regards

Categories