Hello.
The log traces in the submit() methods of the provider classes are misleading, because
they use the word "Received", while the OMM message is sent and not received, e.g.:
loggerMsg
TimeStamp: 09:17:49.687
ClientName: Provider_1
Severity: Verbose
Text: Received RefreshMsg with domain type MarketPrice Domain; handle = 139663545453536, user assigned streamId = 0.
loggerMsgEnd
Regards, Michael Zuck
1
●1 ●2 ●6
misleading log traces in submit()
Hello @miczuc
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If yes, please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
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
9.6k
●10 ●7 ●7
Hello @miczuc
You can submit EMA issue to the development team directly via Refinitiv/Elektron-SDK Github then click "New issue" button. This way makes you can contact and follow up with the development team directly.
79.2k
●251 ●52 ●74
I think that it means that the Provider_1 has received the RefreshMsg with domain type MarketPrice Domain from the application.
It is used to verify what kind of messages sent to the provider object by the application. It doesn't mean that the API has sent this message to the client.
1
●1 ●2 ●6
From point of view of networking it is confusing.
If a request message from a consumer arrives, the log entry is rather similar:
loggerMsg
TimeStamp: 09:17:49.694
ClientName: MarketItemHandler
Severity: Verbose
Text: Received request message.
Stream Id 57
Client handle 30874848
Instance Name Provider_1
loggerMsgEnd
So someone not familiar with this nomenclature may think, there is a process, which is only receiving messages (for me it was also irritating). Ok, it's no so important, since it is only a trace ...
Regards, Michael Zuck
