Date Posted:
Product: TIBCO Spotfire®
Product: TIBCO Spotfire®
Problem:
TIBCO Spotfire Server fails to start and server.log contains error "No node matching the ID from bootstrap.xml"
Solution:
Tibco Spotfire server fails to start even after TSS service has been restarted. In server.log you can see the following line.
FATAL 2017-03-01T09:39:49,106-0500 [*Initialization*] spotfire.server.LifecycleManager: TIBCO Spotfire Server will not be started. No node matching the ID from bootstrap.xml ('74a9a69a-1a35-458b-9436-dbc74205d8d1') found, please re-bootstrap the server. ERROR 2017-03-01T09:39:49,122-0500 [*Initialization*] web.context.ContextLoader: Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'lifecycleManager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.spotfire.server.LifecycleManager]: Constructor threw exception; nested exception is com.spotfire.server.ServerInitializationException: TIBCO Spotfire Server will not be started. No node matching the ID from bootstrap.xml ('74a9a69a-1a35-458b-9436-dbc74205d8d1') found, please re-bootstrap the server. at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:279)
There is mismatch between the actual server_ID and <server-ID> from bootstrap.xml, which is causing the server to not start up properly.
- Stop the TIBCO Spotfire Server service.
- Open TIBCO Spotfire Server Configuration Tool and create and save a new bootstrap.
- Reference: Creating the bootstrap.xml file
- URL: https://docs.tibco.com/pub/spotfire_server/7.8.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-24E553B2-54F9-46BD-A8B7-A1EA914155C0.html
- Review the automatically populated 'Addresses' for the TIBCO Spotfire Server under "Other settings" in the "Bootstrap" tab.
- Start the TIBCO Spotfire Server service.
Comments
0 comments
Article is closed for comments.