TDM Portal error - java.util.MissingResourceException: Can't find bundle for base name messages

Document ID : KB000016016
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

When starting the TDM Portal,  the underlying Java Virtual Machine will use the default locale that is configured for Windows.  Since our support for different locales are limited at this point, you will need to override the default locale for the Portal to work.

Question:

When I try to see the registered objects on TDM Portal, I see no objects on the list. Checking the F12 with the debug information, I see that TDMModelService has some error. Checking the TDMModelService log, I see that the error is related with my Windows Language ES_cl. 

What can I do to fully enable TDM Portal? 

Follow the part of the log that shows the problem… 


[ERROR] [localhost-startStop-4 ] --- [U:][M:][P:] o.s.b.SpringApplication: Application startup failed 
java.util.MissingResourceException: Can't find bundle for base name messages, locale es_CL 
at java.util.ResourceBundle.throwMissingResourceException(Unknown Source) 
at java.util.ResourceBundle.getBundleImpl(Unknown Source) 
at java.util.ResourceBundle.getBundle(Unknown Source) 
at com.ca.tdm.modeling.enums.ReconcileType.<clinit>(ReconcileType.java:17) 
... 89 common frames omitted 

Answer:

If we look at the locale, the workstation has been configured to use a language, like Spanish in the country of Chilie, which is not supported by TDM Portal. If this is the case, you will need to change the settings in your wrapper.conf file. The default location for this file is C:\Program Files\CA\CA Test Data Manager Portal\service\conf.

 

To make this change, just edit your wrapper.conf to add the following entries:

wrapper.java.additional.8=-Duser.country=US

wrapper.java.additional.9=-Duser.language=en 

When making this change, make sure the additional 'numbering' stays in order as shown below. In this case, the -Duser.country is 8  and -Duser.language is 9, so we need to change -DCATDMWEB to 10.


# Java Additional Parameters 
wrapper.java.additional.1=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
# wrapper.java.additional.2=-Djava.util.logging.config.file=..\..\tomcat\conf\logging.properties 
#wrapper.java.additional.3=-Djava.endorsed.dirs=..\common\endorsed 
wrapper.java.additional.2=-Dcatalina.base=..\..\tomcat 
wrapper.java.additional.3=-Dcatalina.home=..\..\tomcat 
wrapper.java.additional.4=-Djava.io.tmpdir="%CATDMWEB_APPDATA%tomcat/temp" 
wrapper.java.additional.5=-Dspring.config.location=..\..\conf\application.properties 
wrapper.java.additional.6=-DCATDMWEB_HOME=..\..\ 
#wrapper.java.additional.6=-Dsolr.solr.home=..\solr 
#wrapper.java.additional.4=-XX:PermSize=256m 
#wrapper.java.additional.5=-XX:MaxPermSize=256m 
wrapper.java.additional.7=-Dorg.springframework.boot.logging.LoggingSystem=com.ca.tdm.utils.TDMLoggingSystem 
wrapper.java.additional.8=-Duser.country=US 
wrapper.java.additional.9=-Duser.language=en 
wrapper.java.additional.10=-DCATDMWEB_APPDATA="%CATDMWEB_APPDATA%." 

 

After you make the change, restart the portal for the change to be loaded. After the portal has started, you should be able to use the portal without this error.