|
Problem(Abstract) |
Unable to start Enterprise JavaBeans (EJB) using container
managed persistence (CMP). The following exceptions are found in
SystemOut.log
[2/4/05 0:51:48:103 EST] 3de90 EJBContainerI E WSVR0062E: Unable to start
EJB, Arc#ArcEntity.jar#Section142Entity: javax.ejb.EJBException: nested
exception is:
com.ibm.ws.ejbpersistence.utilpm.PersistenceManagerException: PMGR1000E:
Exception occurred
:com.ibm.websphere.naming.CannotInstantiateObjectException: Exception
occurred while the JNDI NamingManager was processing a
javax.naming.Reference object. [Root exception is
javax.naming.NameNotFoundException: eis/jdbc/myEJB_CMP [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound]].
at
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.createPMException(Unknown
Source)
at
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.getConnectionFactory(Unknown
Source)
at
com.ibm.ws.ejbpersistence.beanextensions.PMModuleCookieImpl.beanInstall(Unknown
Source)
at
com.ibm.ws.ejbpersistence.beanextensions.PersistenceManagerImpl.beanInstall(Unknown
Source)
at
com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1331)
at
com.ibm.ejs.container.EJSContainer.getHomeWrapperCommon(EJSContainer.java:976)
. . . |
|
|
|
Cause |
When a CMP entity bean starts up, it will try to locate
the CMP connection factory that it is associated with. In this case, the
CMP connection factory does not exist because the data source used was not
enabled for container managed persistence. |
|
|
Resolving the
problem |
Enable the container managed persistence for the data
source by checking the "Use this Data Source in container managed
persistence (CMP)" checkbox in the data source configuration on the
IBM® WebSphere® Application Server Administrative Console.
Save and restart the server. The error should no longer occur. |
|
|