question

Upvotes
Accepted
1 0 0 1

Question related to Case : 05528463

Regarding subject case#.

we are still having issue of fail over function.

The follwing is answer to the case ,

Would you advise us if any missing or any issue.

Thanks,

Tamura

  1. The version of RFA Java that you are using

JSFC version: 3.5.6.10_F32

  1. The full configurations

<Property key="ServerList" value="jpapp2ps1.jpn.nsroot.net jpacp2ps1.jpn.nsroot.net"/>

<Property key="UserName" value="citismrt"/>

<Property key="ServiceName" value="RDFLEX"/>

<Property key="RetryMillis" value="4000"/>

<Property key="ServerList" value="jpapp2ps1.jpn.nsroot.net jpacp2ps1.jpn.nsroot.net"/>

<Property key="UserName" value="citismrt"/>

<Property key="ServiceName" value="IDN_SELECTFEED"/>

treprfarfa-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

1 Answer

Upvotes
Accepted
1.9k 6 9 16

According to JSFC’s configuration guide, the configuration names are case-sensitive (e.g. serverList and username). Therefore, ServerList, UserName, ServiceName, and RetryMillis are not valid from JSFC’s perspective. Especially, ServiceName and RetryMillis do not even exist in the JSFC’s guide at all.

The correct way to set fail-over server in JSFC is that there should be a space character separated between each server name/host name/ip address.

For example,

XConfigDb configDb = new XConfigDb();
...
configDb.addVariable("serverList", "10.42.68.69 localhost 192.168.27.46 192.168.27.48");
...

_session = Session.create(_appId, _configDb);
  • 10.43.68.69 is tried first.
  • localhost is tried second.
  • 192.168.27.46 is tried third.
  • 192.168.27.48 is tried last.

Hope this helps.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Click below to post an Idea Post Idea