question

Upvotes
Accepted
3 3 5 6

What could cause intermittent "Failed to make subscription" StatusMsg

Hi,

I'm using ema-3.4.0.1.jar, sometimes I get "Failed to make subscription" StatusMsg with DataState.SUSPECT data state when subscribing to instruments, the instruments seem fine as subscribing again would work fine although sometimes a few more tries are needed.

So if I subscribe/unsubscribe to some instruments continuously every second, sometimes I get data back, sometimes I get that StatusMsg. What's the likely cause of this error?

elektronrefinitiv-realtimeelektron-sdkema-apirrtelektron-message-apijavastatus
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.

Hello @ahmire.kailer,

Can you share the small excerpt of code that reproduces the issue?

As you mention it happens sometimes, may be helpful to better understand, how often do you see it and did you have a chance to notice when it usually happens?

@ahmire.kailer

Hi,

Thank you for your participation in the forum.

Is the reply below satisfactory in answering your question?

If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.

Otherwise please post again offering further insight into your question.

Thanks,

AHS

Hi,

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

Thanks,

AHS

1 Answer

· Write an Answer
Upvotes
Accepted
32.2k 40 11 20

Hello @ahmire.kailer,

A couple of different ideas here, as I do not recall seeing this message before.

Are you, per chance, subscribing and unsubscribing in rapid succession, from multiple threads, and one action is not completed before l the next action is attempted?

If the case, for your use case, issuing a snapshot, non-streaming request would be more suitable (See Snapshot & Streaming Requests in EMA Developer Guide)?

Examining EMA source code for ESDK 1.4 (you can download the full open source code via Elektron SDK on GitHub) I am not finding this or similar message. Looking at OmmState.java implementation, so not see it. Is the message perhaps originating from custom code? Then you can try to find out more about the cause at the point in custom consumer code where it's being generated.

Another potential way to find out more is to enable tracing via XmlTraceToStdout ( see EMA Config Guide).

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.

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.