Error opening information designer in Spotfire server

Error opening information designer in Spotfire server

book

Article ID: KB0070652

calendar_today

Updated On:

Products Versions
Spotfire Analyst 12.5.0 and 14.0.0

Description

Below error message is observed while opening information designer after installing the Spotfire.
  
ERROR 2024-02-08T16:53:17,054+0400 [*Initialization*] web.context.ContextLoader: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'informationModel' defined in class path resource [applicationContext-tss-is-common.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.spotfire.ws.im.InformationModel]: Factory method 'createInstance' threw exception; nested exception is java.lang.IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread
at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:658) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:638) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1352) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1195) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:582) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans.jar:5.3.27]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:955) ~[spring-beans.jar:5.3.27]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:920) ~[spring-context.jar:5.3.27]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) ~[spring-context.jar:5.3.27]
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:399) ~[spring-web.jar:5.3.27]
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:278) [spring-web.jar:5.3.27]
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:103) [spring-web.jar:5.3.27]
at com.spotfire.ws.server.InformationServicesServerInitializer.contextInitialized(InformationServicesServerInitializer.java:58) [spotfire-server-is.jar:?]

This problem is caused by a known issue with Spotfire where IPv6 addresses get incorrectly configured as server backend address. One may check the online-servers.txt file in the troubleshooting bundle to verify if backend addresses are not set up correctly. You can see below sample(from online-servers.txt generated in troubleshooting bundle with IP addresses masked) the IPv6 addresses are not formatted correctly which is caused by a known issue.

server alias;version;primus;site primus;backend addresses spotfire;14.0.0 LTS;true;true;tibco,2001:AbC:01Oa:Smpl:****:IP**:aDr:****,2001:aBc:123:tEst:****:****:***:****,172.20.**.*

Issue/Introduction

While opening Information Designer on Spotfire, it throws an error: attempt to unlock read lock, not locked by current thread.

Environment

All

Resolution

This issue has been addressed in Spotfire server version 14.0.1. 
See Release notes: TSS-33239 https://docs.tibco.com/pub/spotfire_server/14.0.1/SPOT_sfire_server_14.0.1_relnotes.pdf?id=0

As a workaround, user may follow below to setup correct back-end addresses:
  1. Stop Spotfire server service
  2. On command prompt as an administrator and navigate to spotfire-bin folder. (file location like this: C:\tibco\tss\14.0.0\tomcat\spotfire-bin)
  3. Run below command to set the desired backend address: 
    config set-addresses -Aspotfire -A17*.**.**.**
  4. Run below command and verify if the backend addresses are correct:  
    config list-addresses
  5. Start spotfire server service

Additional Information

Doc: Set address command: Doc: list address command: Release notes: TSS-33239: When Information Services is run as an external process (the default), and one or more
(online) Spotfire Server nodes have IPv6 addresses configured, the Spotfire Server fails
to start.
Powered by Wolken Software