Spotfire Server does not start if there are any issues with the communication to LDAP

Spotfire Server does not start if there are any issues with the communication to LDAP

book

Article ID: KB0076392

calendar_today

Updated On:

Products Versions
Spotfire Server 4.5 and later

Description

The easiest situation is when the configured LDAP servers have been stopped, renamed etc so none of the servers in the configured list can be contacted.
This results in the Spotfire Server eventually stops during startup with:

ERROR ... [*Initialization*] web.context.ContextLoader: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ldapConfigFactory' defined in class path resource [applicationContext.xml]: Bean instantiation via constructor failed; ...
...
INFO ... [*Shutdown*] spotfire.logging.LoggerContextListener: Shutting down the LogManager


After this shutdown of Spotfire, Tomcat and the Windows Service are still running, so it might look like things are fine.
Trying to connect with a browser gives 404 - service not available (since Tomcat does not have any service "Spotfire" running).

Environment

Spotfire Server with LDAP configured as Authentication and/or User Directory.

Resolution

Fix the communication to the LDAP server(s), or change the configuration so there is at lest one working LDAP server in each LDAP configuration (the issue can be in a config you forgot you have).
The server.log have the information you need about which LDAP config that is problematic and which type och communication error there is.

Issue/Introduction

Users get "404 - service not available", but the Windows Service is "running", when the Spotfire Server have failed to start due to failing LDAP communication
Powered by Wolken Software