Monday, March 2, 2015

Database JNDI Configuration Isuuse with Cloudscape DataSource demo


If you have database configuration problem when the WebSphere Commerce Search server is starting, you may see the following error message:

Failed to retrieve datasource for search server with JNDI name: jdbc/WebSphere Commerce Cloudscape DataSource demo.

One reason we saw this message was that the classpath missed the jdbc libraries. The Search server decide to switch to the default data source that is the demo one.


[10/9/14 11:05:32:513 PDT] 00000012 SolrRESTSearc W com.ibm.commerce.foundation.server.services.rest.search.config.solr.SolrRESTSearchDatabaseConfiguration parseElement(Element) WAS configurable namespace binding for Search datasource is not defined. Defaulting to Cloudscape for use with Toolkit.
[10/9/14 11:05:33:069 PDT] 00000012 SolrRESTSearc W com.ibm.commerce.foundation.server.services.rest.search.config.solr.SolrRESTSearchDatabaseConfiguration parseElement(Element) WAS configurable namespace binding for Search datasource is not defined. Defaulting to Cloudscape for use with Toolkit.

com.ibm.commerce.foundation.server.services.dataaccess.exception.ConfigurationException: CWXFS0020E: Failed to retrieve datasource for search server with JNDI name: jdbc/WebSphere Commerce Cloudscape DataSource demo.
at com.ibm.commerce.foundation.server.services.rest.search.config.solr.SolrRESTSearchDataSourceConfigurationFactory.getDefaultDataSource(SolrRESTSearchDataSourceConfigurationFactory.java:155)
at com.ibm.commerce.foundation.internal.common.config.ConfigurationFactory.getDefaultDataSource(ConfigurationFactory.java:203)
at com.ibm.commerce.foundation.internal.server.databaseconnection.J2EEDatabaseConnectionManager.initDataSource(J2EEDatabaseConnectionManager.java:93)
at com.ibm.commerce.foundation.internal.server.databaseconnection.J2EEDatabaseConnectionManager.getConnection(J2EEDatabaseConnectionManager.java:228)
at com.ibm.commerce.foundation.server.services.dataaccess.JDBCQueryService.getConnection(JDBCQueryService.java:1565)

2 comments:

  1. Another cause is if the databse credentials are wrong. I found an FFDC log that revealed a DB2 authentication failure. Resolving that authentication failure made this error go away.

    ReplyDelete

  2. Thanks for sharing this good blog.This is very important and imformative blog for Java .It's very interesting and useful for students
    Java Online Training Hyderabad

    ReplyDelete