Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Finding "Datasource" name

Hi All,

I have created-built-deployed a dictionary DC. Now I want to put the "Datasource" name in my EJB DC's persistence.xml.

While deploying it is showing following warning :-

Dec 12, 2008 12:52:03 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:

[002]Additional log information about the deployment

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.3.7185 - 630]/>

<!NAME[/usr/sap/GGT/JC08/SDM/program/log/sdmcl20081212072149.log]/>

<!PATTERN[sdmcl20081212072149.log]/>

<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>

<!ENCODING[UTF8]/>

<!LOGHEADER[END]/>

Dec 12, 2008 2:21:51 AM Info: -


Starting deployment -


Dec 12, 2008 2:21:51 AM Info: Error handling strategy: OnErrorStop

Dec 12, 2008 2:21:51 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop

Dec 12, 2008 2:21:51 AM Info: Update strategy: UpdateAllVersions

Dec 12, 2008 2:21:51 AM Info: Starting deployment prerequisites:

Dec 12, 2008 2:21:53 AM Info: Loading selected archives...

Dec 12, 2008 2:21:53 AM Info: Loading archive '/usr/sap/GGT/JC08/SDM/program/temp/temp15006sap.com~ja_rnumapp.ear'

Dec 12, 2008 2:21:57 AM Info: Selected archives successfully loaded.

Dec 12, 2008 2:21:57 AM Info: Actions per selected component:

Dec 12, 2008 2:21:57 AM Info: Update: Selected development component 'ja_rnumapp'/'sap.com'/'local'/'20081212125113'/'0' updates currently deployed development component 'ja_rnumapp'/'sap.com'/'local'/'20081212124955'/'0'.

Dec 12, 2008 2:21:57 AM Info: Ending deployment prerequisites. All items are correct.

Dec 12, 2008 2:21:57 AM Info: Saved current Engine state.

Dec 12, 2008 2:21:57 AM Info: Starting: Update: Selected development component 'ja_rnumapp'/'sap.com'/'local'/'20081212125113'/'0' updates currently deployed development component 'ja_rnumapp'/'sap.com'/'local'/'20081212124955'/'0'.

Dec 12, 2008 2:21:57 AM Info: SDA to be deployed: /usr/sap/GGT/JC08/SDM/root/origin/sap.com/ja_rnumapp/local/0/20081212125113/temp15006sap.com~ja_rnumapp.ear

Dec 12, 2008 2:21:57 AM Info: Software type of SDA: J2EE

Dec 12, 2008 2:21:57 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Dec 12, 2008 2:22:22 AM Info: Begin of log messages of the target system:

08/12/12 02:21:57 - ***********************************************************

08/12/12 02:21:57 - Start updating EAR file...

08/12/12 02:21:57 - start-up mode is lazy

08/12/12 02:21:57 - EAR file updated successfully for 63ms.

08/12/12 02:21:57 - Start updating...

08/12/12 02:21:58 - EAR file uploaded to server for 353ms.

08/12/12 02:22:19 - Successfully updated. Update took 21174ms.

08/12/12 02:22:19 - Deploy Service status:

08/12/12 02:22:19 - Application : sap.com/ja_rnumapp

08/12/12 02:22:19 -

08/12/12 02:22:19 - AUTONUMSESSIONBean - EJB

08/12/12 02:22:19 - TMP_AUTONUMBean - EJB

08/12/12 02:22:19 - WEB SERVICE PORTS:

/GenerateReqID1/GenerateReqID1Config1

- WEBSERVICES

08/12/12 02:22:19 - GenerateReqID1/GenerateReqID1Config1 - WEB

08/12/12 02:22:19 - ***********************************************************

Dec 12, 2008 2:22:22 AM Info: End of log messages of the target system.

Dec 12, 2008 2:22:22 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Dec 12, 2008 2:22:22 AM Warning: Finished with warnings: development component 'ja_rnumapp'/'sap.com'/'local'/'20081212125113'/'0':

Caught exception during application startup from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Error occurred while starting application sap.com/ja_rnumapp and wait.

Reason: Clusterwide exception: server ID 84822150:com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: The DataSource for PersistenceManager CONFIG_DB is not created.

at com.sap.engine.services.ejb.entity.pm.PersistenceManager.initDataSource(PersistenceManager.java:217)

at com.sap.engine.services.ejb.EJBAdmin.commitLoad(EJBAdmin.java:1119)

at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2445)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/cmp/tx/sap.com/ja_rnumapp/CONFIG_DB, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "CONFIG_DB" does not exist. Possible reasons: the connector in which ConnectionFactory "CONFIG_DB" is defined is not deployed or not started.]

at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)

at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)

at javax.naming.InitialContext.lookup(InitialContext.java:347)

at javax.naming.InitialContext.lookup(InitialContext.java:347)

at com.sap.engine.services.ejb.entity.pm.PersistenceManager.initDataSource(PersistenceManager.java:185)

... 21 more

Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "CONFIG_DB" does not exist. Possible reasons: the connector in which ConnectionFactory "CONFIG_DB" is defined is not deployed or not started.

at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)

at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)

at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)

at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)

at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)

at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)

... 25 more

Also can anybody please tell me how to locate which database to see in order to see the generated table?

Thanks and regards,

Amey Mogare

Not what you were looking for? View more on this topic or Ask a question