question

Upvotes
Accepted
20 7 8 11

ADS 2.6.3 - DACS 6.6 - RFA Java - Network connection to DACS Multiplexer down

Hi All

ADS2.6.3

DACS6.6

RFA Java

Multiple RFA apps already connected with no issues.

Restarted one of them to make sure no issues have been introduced since they last connected and had no issues.

New RFA Java app attempting to connect to ADS and getting the following error -

30.Aug.18 18:01:45:159 [Thread-9] DEBUG - Received ENTITLEMENTS_AUTHENTICATION_EVENT: { state: LOGGED_OUT, code: ENTITLEMENTS_SYSTEM_NOT_AVAILABLE, text: "Network connection to DACS Multiplexer down"}

Has anyone come across this before and got any suggestions as to what the issue might be?
treprfarfa-apiDACSmultiplexing
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.

@Paul.Wuethrich2

Hi,

Thank you for your participation in the forum.

Is the reply below satisfactory in resolving your query?

If yes please click the 'Accept' next to the 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

@Paul.Wuethrich2

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
9.6k 10 7 7

Hello @Paul.Wuethrich2

An RFA application can receive “Network connection to DACS Multiplexer down” error when RFA cannot establish a connection to a local DACS sink daemon for performing the local entitlement(RFA used by the application performs entitlement with DACS via DACS sink daemon)

If DACS sink daemon, Multiple RFA apps and New RFA Java app run on the same machine but only the New RFA Java app shows the error, the number of Sink Clients(RFA Java app) that can connect to the DACS sink daemon reaches to the maximum already before the New RFA Java app starts. After that the New RFA Java app cannot connect to it and the error is shown. To protect the error in this case, increase the value of DACS_MAX_SNKD_CLIENTS parameters in dacs.env file read by DACS sink daemon. For example, to increase from 8 to 12.

DACS_MAX_SNKD_CLIENTS=12; export DACS_MAX_SNKD_CLIENTS 

Then, save the file and restart DACS sink daemon to take the affect of the changed parameter.

If New RFA Java app runs on the difference machine from the others, please make sure that DACS sink daemon is running on the same machine as New RFA Java app.

Normally, the RFA applications connecting to ADS use remote entitlement(ADS performs entitlement and it communicates with a DACS sink daemon) not local entitlement which you are using. Local entitlement is for the RFA applications connecting to RTIC since RTIC does not support DACS feature. Hence, I recommend you ask your ADS admin to enable DACS feature on ADS. Then, you can ignore this error message because ADS connects to DACS sink daemon and performs entitlement instead of RFA. If your ADS admin require any help about enabling DACS feature on ADS, they can submit the query to ADS support team via My Account . For any difficulties submitting the query, please contact Thomson Reuters Account team.

To set the user info in RFA application for remote entitlement, the application needs to use TokenizedPrincipalIdentity class. For an example application source code, please refer to MDSubDemo located in [RFA_Java_Package]\Legacy\Examples\com\reuters\rfa\legacyexample\session\mdsub.

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.