Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

FacesConfig warning messages in the log

SA-1991

Summary



Below are the warning messages appear in the server console/log.
1)

WARNING: Locale name in faces-config.xml null or empty, setting locale to default locale : en

2)
<Sep 23, 2014 6:23:15 PM EDT> <Warning> <Weblogic-Validation> <BEA-2156400> <The validation.xml file, located at file:/_WL_user/dma_wls_ora/k6su07/war/WEB-INF/validation.xml, does not conform to the JSR 303 specifications.>

3)
The application is using ServletContainerInitializer class com.sun.jersey.server.impl.container.servlet.JerseyServletContainerInitializer that is loaded from:file:/_WL_user/dma_wls_ora/k6su07/war/WEB-INF/lib/jersey-bundle-1.17.jar. This initializer overrides the one available in the system.


Error Messages



NA


Steps to Reproduce



Server startup


Root Cause



Optional configuration parameters missing in the faces-config file.
    

Resolution



1) WARNING: Locale name in faces-config.xml null or empty, setting locale to default locale : en

Out-Of-The-Box(OOTB) faces-config.xml doesn't have an entry for default locale hence, this warning message stating that default locale has been observed. This is an optional tag in the faces-config.xml. This warning message can be ignored and it doesn't have any impact on the business functionality.

In order to avoid this warning message then add the <locale-config> tag in the faces-config.xml file with the appropriate locale.

<application>
<locale-config>
<default-locale>en</default-locale>
</locale-config>
</application>

2) <Warning> <Weblogic-Validation> <BEA-2156400> <The validation.xml file, located at file/_WL_user/dma_wls_ora/k6su07/war/WEB-INF/validation.xml, does not conform to the JSR 303 specifications.>

OOTB Deployment Manager (DMa) application uses the Apache Commons validator framework to validate the Java Beans and it was not compliant with Java Specification Requests (JSR). JSR 303 specifications is introduced in Java SE and EE version 6 onwards. Hence in weblogic 12c version, this warning message appears.

This warning message can be ignored as it doesn't harm any functionality.

3) The application is using ServletContainerInitializer class com.sun.jersey.server.impl.container.servlet.JerseyServletContainerInitializer that is loaded from:file:/_WL_user/dma_wls_ora/k6su07/war/WEB-INF/lib/jersey-bundle-1.17.jar. This initializer overrides the one available in the system.

Weblogic 12c contains the older version of jersey-bundle_1.0.0.0_1-1-5-1.jar in its classpath and DMa application is overriding with the latest jersey-bundle-1.17.jar. Hence, the above message appears in the logs. This message is not harmful to any of the functionality and it can be ignored.
 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us