Spotfire Servers in an Clustered setup may fail to start during the initial setup.

book

Article ID: KB0137603

calendar_today

Updated On:

Products	Versions
TIBCO Spotfire Server	ALL

Description

If you have multiple Spotfire servers in a cluster, then on starting the second server, both the Spotfire servers will be unavailable and may not start.

You will also see similar warnings, as shown below, in the logs

WARN 2024-10-03T13:20:13,174-0400 [] ignite.internal.diagnostic: Failed to wait for partition map exchange [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], node=1fa4ec06-7ee8-42f1-8a22-662b7dc5ebc1]. Consider changing TransactionConfiguration.txTimeoutOnPartitionMapExchange to non default value to avoid this message. Dumping pending objects that might be the cause:

WARN 2024-10-03T13:19:42,223-0400 [*Initialization*] ignite.internal.IgniteKernal%Spotfire: Default character encoding is windows-1252. Specify UTF-8 character encoding by setting -Dfile.encoding=UTF-8 JVM parameter. Differing character encodings across cluster may lead to erratic behavior.

Environment

ALL

Resolution

The above issue is seen because the IPV4 Stack is not set to true, and even the UTF-8 encoding is not set. You will have to follow the below steps to enable UTF-8 and set -Djava.net.preferIPv4Stack=true and resolve the issue.

1) Browse to "<Spotfire installation folder>\tomcat\spotfire-bin" from the Windows command line.

2) Execute the command to export the configuration> config.bat export-config -f

3)Stop both the Spotfire Servers

3) Run the command> config.bat config-external-ignite-process --jvm-opts-XX:+AlwaysPreTouch --jvm-opts-XX:+UseG1GC --jvm-opts-XX:+ScavengeBeforeFullGC --jvm-opts-XX:+DisableExplicitGC --jvm-opts-Djava.net.preferIPv4Stack=true --jvm-opts-Dfile.encoding=UTF-8

4) Import the configuration> config.bat import-config -c "Updated external Ignite Process variables'

5)Attempt to start the second server that is failing first, and then start the other server.