We have an application using EMA 3.6.1.2 and connected to ADS 3.5.1 for item subscription. The connection was dropped after awhile, but there was no error message on API / application end. Could you please advise on how to enable advanced logging or debugging that we can find what was the root cause of disconnection? Thanks.
87.5k
●294 ●53 ●79
Please refer to the Enterprise Message API (EMA) - Configuration Overview article in the Logger Configuration section regarding enabling logging in EMA.
If you are using EMA Java, you can also refer to the How to integrate Enterprise Message API Java edition with Log4j Logging Framework article.
However, you may need to check the ADS log file. If ADS cuts the connection, you will state the reason in the ADS log file.
1
●0 ●1 ●1
hi @Jirapongse, we have enabled trace logs, in ADS we see application disconnected after a while, see as below screenshot
Or client doesn't ping logs in ADS
In client logs, we see it is reconnected with refreshMsg, but after that no rates incomming
loggerMsg ClientName: LoginCallbackClient Severity: Trace Text: RDMLogin stream was open with refresh message LoginRefresh: streamId: 1 name: EDGE_flexi_UAT nameType: 1 State: Open/Ok/None - text: "Login accepted by host ip-10-116-hub1." isSolicited: true applicationId: 256 applicationName: ADS position: 192.168.24.101/flexi-refinitiv-rate-service-sit-24-9gt5p providePermissionProfile: 0 providePermissionExpressions: 1 singleOpen: 1 allowSuspectData: 1 supportBatchRequests: 1 supportBatchReissues: 1 supportBatchCloses: 1 supportOMMPost: 1 supportOptimizedPauseResume: 0 supportStandby: 0 supportViewRequests: 1 supportEnhancedSymbolList: 1 loggerMsgEnd
