After you upgrade to SAS Visual Investigator 10.8, the following text-mining services fail to start:
- sas-viya-textcategorization-default
- sas-viya-textconcepts-default
- sas-viya-textparsing-default
- sas-viya-textsentiment-default
- sas-viya-texttopics-default
You then see these log messages:
The bean 'entityManagerFactory', defined in class path resource [com/sas/commons/db/tenancy/hibernate/config/MultiTenantConnectionProviderAutoConfiguration.class], could not be registered.
A bean with that name has already been defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class] and overriding is disabled.
This problem impacts only multi-tenant deployments. The workaround is to set the property -Dspring.main.allow-bean-definition-overriding=true for the text-mining services, as shown here:
source /opt/sas/viya/config/consul.conf
export CONSUL_HTTP_TOKEN=$(sudo cat /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token)
/opt/sas/viya/home/bin/sas-bootstrap-config kv write –force config/textCategorization/jvm/java_option_allow_bean_overriding "-Dspring.main.allow-bean-definition-overriding=true"
/opt/sas/viya/home/bin/sas-bootstrap-config kv write –force config/textConcepts/jvm/java_option_allow_bean_overriding "-Dspring.main.allow-bean-definition-overriding=true"
/opt/sas/viya/home/bin/sas-bootstrap-config kv write –force config/textParsing/jvm/java_option_allow_bean_overriding "-Dspring.main.allow-bean-definition-overriding=true"
/opt/sas/viya/home/bin/sas-bootstrap-config kv write –force config/textSentiment/jvm/java_option_allow_bean_overriding "-Dspring.main.allow-bean-definition-overriding=true"
/opt/sas/viya/home/bin/sas-bootstrap-config kv write –force config/textTopics/jvm/java_option_allow_bean_overriding "-Dspring.main.allow-bean-definition-overriding=true"
Use these commands to verify that the property -Dspring.main.allow-bean-definition-overriding=true is set:
/opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token kv read --recurse config/textCategorization/jvm
/opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token kv read --recurse config/textConcepts/jvm
/opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token kv read --recurse config/textParsing/jvm
/opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token kv read --recurse config/textSentiment/jvm
/opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token kv read --recurse config/textTopics/jvm
Then use these commands to restart the text-mining services:
systemctl restart sas-viya-textcategorization-default
systemctl restart sas-viya-textconcepts-default
systemctl restart sas-viya-textparsing-default
systemctl restart sas-viya-textsentiment-default
systemctl restart sas-viya-texttopics-default
A hot fix is planned for this issue.
Operating System and Release Information
| SAS System | SAS Visual Investigator | Linux for x64 | 10.8 | | Viya | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.