Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

NamingException Error on WebSphere 6.x

Written By

Alberto Montero

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

This article is a legacy article. It applies to previous versions of the Liferay product. While the article is no longer maintained, the information may still be applicable.

When Liferay Portal is running on a Websphere Application Server 6, a NamingException error is thrown.

Example:

0000001b Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow: Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl Context method: bind Context name: ddgdsa36Cell01/clusters/L_RAY_CLUSTER Target name: java_liferay:jdbc/LiferayPool Other data: Object to bind: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource@3a7aa198 Exception stack trace: javax.naming.NamingException: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getReference() returned null in violation of the JNDI API at com.ibm.ws.naming.util.Helpers.processJavaObjectForBinding(Helpers.java:604) at com.ibm.ws.naming.jndicos.CNContextImpl.doBind(CNContextImpl.java:1911) at com.ibm.ws.naming.jndicos.CNContextImpl.bind(CNContextImpl.java:682) at com.ibm.ws.naming.util.WsnInitCtx.bind(WsnInitCtx.java:205) at com.ibm.ws.naming.util.WsnInitCtx.bind(WsnInitCtx.java:217) at javax.naming.InitialContext.bind(InitialContext.java:400)

Resolution

This is actually an issue with WebSphere.

  1. Navigate to WAS_HOME/profiles/<profile-name>/properties
  2. Open the sas.clients.props file
  3. Change the com.ibm.CORBA.validateBasicAuth= from false to true
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?