Skip to main content

One of the TIBCO Spotfire Servers in the cluster fails to start

Rich Talbot
  • Created
Date Posted:
Product: TIBCO Spotfire®

Problem:

One of the TIBCO Spotfire Servers in the cluster fails to start


Solution:

When setting up a cluster of TIBCO Spotfire Servers, you have successfully added multiple TIBCO Spotfire Servers. You are able to start one of the Spotfire servers but have issues when you start the second server. On the second server, look at catalina.log file and you may see the following: 

26-Oct-2017 11:06:27.004 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Spotfire
26-Oct-2017 11:06:27.004 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.43
26-Oct-2017 11:06:30.801 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing com.spotfire.server.root.RootHttpMethodsFilter
26-Oct-2017 11:06:30.895 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:\tibco\tss\7.8.1\tomcat\webapps\spotfire
26-Oct-2017 11:06:45.975 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath
26-Oct-2017 11:06:45.991 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing logging using configuration file 'C:\tibco\tss\7.8.1\tomcat\webapps\spotfire\WEB-INF\log4j.properties'
26-Oct-2017 11:06:48.320 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring root WebApplicationContext
26-Oct-2017 11:06:52.666 INFO [localhost-startStop-1] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-9080"]
26-Oct-2017 11:06:52.666 INFO [localhost-startStop-1] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-9443"]
26-Oct-2017 11:07:00.467 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:07:04.983 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:07:30.809 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:07:36.124 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:07:52.784 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:08:28.364 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:09:35.804 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:09:37.008 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:10:30.472 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:10:38.595 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.
26-Oct-2017 11:10:46.380 INFO [localhost-startStop-1] com.hazelcast.config.XmlConfigLocator.null Loading 'hazelcast-default.xml' from classpath.

  This indicates that you have an issue with the bootstrap. The server ID may be same on first and second Spotfire server. Create a new bootstrap file to resolve the issue. See the referenced documentation for instructions. Doc: Creating the bootstrap.xml file

Comments

0 comments

Article is closed for comments.