Forum Stats

  • 3,815,712 Users
  • 2,259,070 Discussions
  • 7,893,213 Comments

Discussions

Need database JTA service connected to java service

Michael OBrien
Michael OBrien Member Posts: 26 Blue Ribbon
edited Jun 21, 2013 6:52AM in Java Cloud Service

Hi,

   In my trial the database service was already connected up to my java service and showed in the data sources window.

   In my paid service the connection is not made - therefore my JPA datasource is not resolving  - as expected until this is fixed.

   Could you join the 2 services or direct myself to a way to manually join them.

   thank you

   /michael

   obrienlabs.org

Exception: Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.ValidationException Exception Description: Cannot acquire data source [database]. Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'database'. Resolved ''; remaining name 'database' javax.persistence.PersistenceException: Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.ValidationException Exception Description: Cannot acquire data source [database]. Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'database'. Resolved ''; remaining name 'database'at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:517)at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)at com.vision.cloud.jpa.VisitorServlet.readData(VisitorServlet.java:238)at com.vision.cloud.jpa.VisitorServlet.processRequest(VisitorServlet.java:141)at com.vision.cloud.jpa.VisitorServlet.doGet(VisitorServlet.java:355)at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:165)at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)at weblogic.servlet.security.internal.WebGateRedirectFilter.doFilter(WebGateRedirectFilter.java:178)at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.ValidationException Exception Description: Cannot acquire data source [database]. Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'database'. Resolved ''; remaining name 'database'at org.eclipse.persistence.exceptions.ValidationException.cannotAcquireDataSource(ValidationException.java:497)at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:109)at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:330)at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:293)at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connect(DatasourceAccessor.java:418)at org.eclipse.persistence.sessions.server.ConnectionPool.buildConnection(ConnectionPool.java:216)at org.eclipse.persistence.sessions.server.ExternalConnectionPool.startUp(ExternalConnectionPool.java:146)at org.eclipse.persistence.sessions.server.ServerSession.connect(ServerSession.java:484)at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login(DatabaseSessionImpl.java:633)at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:208)at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)... 38 more Caused by: javax.naming.NameNotFoundException: Unable to resolve 'database'. Resolved ''; remaining name 'database'at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:402)at javax.naming.InitialContext.lookup(InitialContext.java:396)at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:103)

... 48 more

Answers

This discussion has been closed.