If you have database configuration problem when the WebSphere Commerce Search server is starting, you may see the following error message:
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.
Failed to retrieve datasource for search server with JNDI name: jdbc/WebSphere Commerce Cloudscape DataSource demo.
[10/9/14 11:05:32:513 PDT] 00000012 SolrRESTSearc W com.ibm.commerce.foundation. server.services.rest.search. config.solr. SolrRESTSearchDatabaseConfigur ation 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. SolrRESTSearchDatabaseConfigur ation 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. SolrRESTSearchDataSourceConfig urationFactory. getDefaultDataSource( SolrRESTSearchDataSourceConfig urationFactory.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)
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
ReplyDeleteThanks 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