TIBCO Spotfire Server fails to start with error "No public HTTP endpoint(s) found or configured"

TIBCO Spotfire Server fails to start with error "No public HTTP endpoint(s) found or configured"

book

Article ID: KB0079725

calendar_today

Updated On:

Products Versions
Spotfire Server 7.5 and Higher

Description

The TIBCO Spotfire Server fails to start with the error "No public HTTP endpoint(s) found or configured" seen in the server.log. For example: 
SEVERE: Exception sending context initialized event to listener instance of class com.spotfire.server.lifecycle.SpotfireServerInitializer
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'connectorConfiguration' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is com.spotfire.server.ServerInitializationException: No public HTTP endpoint(s) found or configured
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299)

 

Issue/Introduction

This article explains the cause of the error "No public HTTP endpoint(s) found or configured" in server.log during TIBCO Spotfire Server start up

Resolution

When there is proxy in the network communication and the TIBCO Spotfire Server public address has not been configured then this error may occur. The public address is used when generating absolute URLs and must be configured if the Spotfire Server is accessed through a load balancer or reverse proxy.

To resolve this issue follow the below steps to configure the public address:

Version 7.9 and higher:
  1. Export the configuration using the below command 
    config export-config --force
  2. Run following command to configure the public address 
    config set-public-address  --url=https://<spotfireserverurl>
  3. Import configuration back by running the following command 
    config import-config -c "configured public address"
  4. Restart the TIBCO Spotfire Server service
  5. Stop and start Web Player service

Version 7.8:
  1. Export the configuration using the below command 
    config export-config --force
  2. Run following command to configure the public address 
    config config-public-address --enabled=true --url=https://<spotfireserverurl>
  3. Import configuration back by running the following command 
    config import-config -c "configured public address"
  4. Restart the TIBCO Spotfire Server service
  5. Stop and start Web Player service

Version 7.7 and lower:
  1. Export the configuration using the below command 
    config export-config --force
  2. Run following command to configure the public address 
    config config-public-endpoint --enabled=true  --url=https://<spotfireserverurl>
  3. Import configuration back by running the following command 
    config import-config -c "configured public address"
  4. Restart the TIBCO Spotfire Server service
  5. Stop and start Web Player service

Additional Information

Doc: set-public-address Doc: config-public-address Doc: config-public-endpoint
Powered by Wolken Software