Tuesday, March 13, 2012

Datasource demo Error

Following errors are seen after deployment


javax.naming.NameNotFoundException: Context: name: jdbc/WebSphere Commerce DB2 DataSource demo: First component in name WebSphere Commerce DB2 DataSource demo not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]

servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet *.jsp in application Exception created : com.ibm.websphere.servlet.error.ServletErrorReport: com.ibm.commerce.exception.ECSystemException: The following command exception has occurred during processing: "com.ibm.ws.naming.util.InvalidObjectException: Some object reference in the name [EJBName]Home" relative to the context "clusters/WC_comm01" is invalid. Some possible causes include a context binding in the name which refers to a destroyed context, or an object binding which contains an invalid EJBHome reference. [Root exception is org.omg.CORBA.INV_OBJREF: Could not resolve IOR string. vmcid: 0x0 minor code: 0 completed: No]".


This happens when multiple data sources are bound during deployment.
To fix this, go to profiles/[DeploymentManagerdirectory]/config/cells//applications/WC_.ear/deployments/WC_/WebSphereCommerceServerExtensionsData.jar/META-INF

Open ibm-ejb-bnd.xmi file. Look for multiple data sources/CMP Connection factory. Remove the Datasource demo factory or one of the datasource as the case may be.

Synchronize the nodes from WAS Console.

1 Comments:

At Friday, April 20, 2012 7:23:00 AM, Anonymous Anonymous said...

This seems to have helped solve my problem, thanks!

 

Post a Comment

<< Home