constantly calling "processTimeSeriesInfo". The function "processTimeSeriesComplete" is not called.
Hello,
I'm trying to consume "ric" with "series = ista.getSeries(XXXXReutersTimeSeriesClient, ista.getSession(), vbr[i].getVirbaseTypeRuter(), period, beginDate, endDate);"
I am checking "isError", "isComplate", "isInfo" in "while" loop.
On my "local" computer, "isComplate" takes the value true, but when I deploy the codes to the server, the "isInfo" condition always works. The "isComplate" condition doesn't work at all.
Even though I gave the necessary ip access permissions to the server, the situation did not change.
Even though I created a user on behalf of "root", which is the user of the server, on the Dacs side and gave him the necessary permissions, the situation did not change.
When I look at the logs of Dacs, I can't find any information about the rics that I have successfully pulled from my local computer, nor about the rics that I have not been able to pull from the server.
Best Answer
-
Hi @Jirapongse,
The error was resolved when the blocked url was allowed and the user information was set as below.
configDb.addVariable("username ", "username.usersurname");
Thank you very much for your help.
1
Answers
-
@SelcukYAPICI
Please confirm the API that you are using. Is it SFC?
1 -
I don't know, but when I examine the project, I see that "jsfc_rmds", "jsfcex_p2ps" and "jsfcex_rmds" jars are used.
0 -
Thanks for reaching out to us.
It is SFC Java.
Typically, the processTimeSeriesInfo callback function can provide additional information via the TimeSeries.text() method, as shown below.
public void processTimeSeriesInfo(TimeSeries ser)
{
_area.append(ser.text());
_area.append(":Info\n");
}For example, the "processing comms fault" text indicates that the API cannot establish a connection to the server. You need to check the text in the processTimeSeriesInfo function.
I can enable tracing in the JSFC API with the following configurations.
*mountTrace : True
*traceSelector : DEBUG
*ipcTraceFlags : 7We may be able to verify what the problem is via the trace log.
I hope that this information is of help.
0 -
Hello Jirapongse,
First of all I want to thank you for your help.
I don't understand what the "_area" variable is. Because I don't know, how do I enable JSFC API configuration. I printed "timeSeries.text()" as below.
@Override
public void processTimeSeriesInfo(TimeSeries timeSeries) {
System.out.println("processTimeSeriesInfo()");
System.out.println(timeSeries.text());
System.out.println(":Info\n");
this.timeSeries = timeSeries;
info = true;
}The result was as follows.
processTimeSeriesInfo()
processing comms fault
:InfoWhat should I understand here?
I think the most important difference between my local computer(it is running properly in my local computer) and the server is the user name.
I learn user name in server like below:
System.out.println("user.name :" + System.getProperty("user.name"));
Server's user name is "root". I create user for the "root" in dacs but it didn't work.
Could it be another user where the server goes to dacs? or do I have another problem?
0 -
To verify what the problem is, you need to enable tracing the API.
If the username is invalid, we will see it in the tracing. For example:
Apr 03, 2023 2:31:33 PM com.reuters.ssl.api.SSLLogger traceMount
FINE:
Thread: JSFC Event Thread 0
Connection 0
Session Rejected: U8009686, unknown to system.
<com.reuters.sfc.examples.timeSeriesDump.TimeSeriesDump : Warning : Apr 3, 2023, 2:31:33 PM>
U8009686, unknown to system.
<com.reuters.sfc.examples.timeSeriesDump.TimeSeriesDump : Info : Apr 3, 2023, 2:31:33 PM>
processing comms fault, location: 127.0.0.1
Apr 03, 2023 2:31:33 PM com.reuters.ssl.api.SSLLogger traceMount
FINE:
Thread: JSFC Event Thread 0
Connection 0
Transport disconnected: U8009686, unknown to system.0 -
Hi @Jirapongse,
I have found that how do I enable JSFC API configuration. the result is as below:
processTimeSeriesInfo()
processing comms fault
:Info
Nis 03, 2023 10:31:55 ÖÖ com.reuters.ssl.api.SSLLogger traceMount
FINE:
Thread: SipcConnectorThread 0
Connection 0
Trying connect to tcp://abcdefghj.abc.abc.ab:8101
Connecting with CONNECTION_VERSION_47
Nis 03, 2023 10:32:05 ÖÖ com.reuters.ssl.api.SSLLogger traceMount
FINE:
Thread: JSFC Event Thread 0
Connection 0
Transport disconnected: Connect attempt timeout
Nis 03, 2023 10:32:05 ÖÖ com.reuters.ssl.api.SSLLogger traceMount
FINE:
Thread: JSFC Event Thread 0
Connection 0
Will try to reconnect in 10 seconds
<ab.abc.abcdef.reuters.soa.custom.ista : Info : Apr 3, 2023, 10:32:05 AM>
processing comms fault, location: abcdefghj.abc.abc.abI look forward to your comments.
0 -
According to the tracing information, the server name looks strange (abcdefghj.abc.abc.ab).
Trying connect to tcp://abcdefghj.abc.abc.ab:8101
Connecting with CONNECTION_VERSION_47
Nis 03, 2023 10:32:05 ÖÖ com.reuters.ssl.api.SSLLogger traceMount
FINE:
Thread: JSFC Event Thread 0
Connection 0
Transport disconnected: Connect attempt timeout
Nis 03, 2023 10:32:05 ÖÖ com.reuters.ssl.api.SSLLogger traceMount
FINE:
Thread: JSFC Event Thread 0
Connection 0
Will try to reconnect in 10 seconds
<ab.abc.abcdef.reuters.soa.custom.ista : Info : Apr 3, 2023, 10:32:05 AM>
processing comms fault, location: abcdefghj.abc.abc.abTypically, the server name is configured via the *serverList configuration. For example:
*serverList : 127.0.0.1
0 -
Hi @Jirapongse,
I changed the server name because posting on the forum may cause problems. The name in tracing information is a url, not a Ip. A valid url. Does it have to be a IP?
0 -
Okay. Yes, I can be either hostname or IP address.
According to the log, the API is unable to connect to that server.
You can test the connection on the machine by using the ping and telnet commands to the 8101 TCP port. For example, my ADS server is running on 192.168.27.49.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛