Tnx Romain! In fact I was having a version conflict with JAXB. Now that this problem is solved, I'm back at the initial situation: the server starts without errors (accessing successfully the database):
http://pastebin.com/3SxJWxUQ but when i access the webapp via browser, the error occurs when accessing the database: http://pastebin.com/R2hAKFmY (the behaviour is the same in TomEE+1.5.1, TomEE+1.5.2-SNAPSHOT and TomEE+1.6.0-SNAPSHOT) On Wed, Mar 6, 2013 at 5:56 PM, Romain Manni-Bucau <[email protected]> wrote: > do you provide a jaxb version? > > if no can you share a sample reproducing the issue? > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/3/6 Bruno Klava <[email protected]> > >> Hi, >> >> I'm already configuring the database via tomee.xml. >> I've tried to use the snapshots below: >> >> 1. Using the snapshot >> apache-tomee-1.5.2-20130306.041201-74-plus.tar.gz, the server fails to >> start: >> >> http://pastebin.com/NSXcxSX4 >> >> 2. Using the snapshot >> apache-tomee-1.6.0-20130306.041135-21-plus.tar.gz, the server starts >> (with some errors): >> >> http://pastebin.com/tJzQPMMA >> >> but fails to connect to the database: >> >> http://pastebin.com/z9QSUV5C >> >> >> Any other idea? >> Tnx! >> >> On Fri, Mar 1, 2013 at 5:51 PM, Romain Manni-Bucau >> <[email protected]> wrote: >> > Hi >> > >> > Maybe try the snapshot and using tomee.xml >> > Le 1 mars 2013 21:48, "Bruno Klava" <[email protected]> a écrit : >> > >> >> Hi folks, >> >> >> >> I'm migrating an existing web application to run on TomEE (I'll use >> >> JMS features of it). >> >> >> >> Our database layer is based on hibernate and is configured via JNDI >> >> using the org.hibernate.connection.DatasourceConnectionProvider. >> >> >> >> In order to access the database, I mapped the resource configuration >> >> done in <Tomcat-WTP-Config>/context.xml to >> >> <TomEE-WTP-Config>/tomee.xml >> >> >> >> The problem is: when I run the app in TomEE, when the server starts, >> >> the database is accessed correctly: >> >> >> >> 17:03:52.189 [INFO ] Initializing connection provider: >> >> org.hibernate.connection.DatasourceConnectionProvider >> >> [o.h.c.ConnectionProviderFactory:173] [localhost-startStop-1] >> >> 17:03:52.195 [INFO ] JNDI InitialContext properties:{} >> >> [org.hibernate.util.NamingHelper:49] [localhost-startStop-1] >> >> 17:03:52.196 [INFO ] Using datasource: java:comp/env/jdbc/dbvms >> >> [o.h.c.DatasourceConnectionProvider:84] [localhost-startStop-1] >> >> >> >> but after that, when I access the app via browser, the database >> >> configuration is loaded again, but this time with error: >> >> >> >> 17:05:43.001 [INFO ] Initializing connection provider: >> >> org.hibernate.connection.DatasourceConnectionProvider >> >> [o.h.c.ConnectionProviderFactory:173] [ajp-bio-8009-exec-1] >> >> 17:05:43.001 [INFO ] JNDI InitialContext properties:{} >> >> [org.hibernate.util.NamingHelper:49] [ajp-bio-8009-exec-1] >> >> 17:05:43.008 [ERROR] Could not find datasource: >> >> java:comp/env/jdbc/dbvms [o.h.c.DatasourceConnectionProvider:78] >> >> [ajp-bio-8009-exec-1] >> >> javax.naming.NameNotFoundException: Name [jdbc/dbvms] is not bound in >> >> this Context. Unable to find [jdbc]. >> >> >> >> Any idea what is going on wrong? >> >> >> >> I found it strange that the database configuration was reloaded after >> >> accessing the app via browser. >> >> >> >> When running the app in Tomcat, the database configuration is not >> >> loaded when the server starts, only after I access the app via >> >> browser. >> >> >> >> Another additional information that i don't know if it related to this >> >> problem: during the TomEE initialization these exceptions are being >> >> thrown: >> >> >> >> 01/03/2013 17:04:48 org.apache.tomee.catalina.TomcatWebAppBuilder >> safeBind >> >> SEVERE: Error in safeBind method >> >> javax.naming.NameNotFoundException: No ORB registered with the OpenEJB >> >> system >> >> at >> >> >> org.apache.openejb.core.ivm.naming.SystemComponentReference.getObject(SystemComponentReference.java:38) >> >> at >> >> >> org.apache.openejb.core.ivm.naming.Reference.getContent(Reference.java:40) >> >> at >> >> >> org.apache.xbean.naming.reference.SimpleReference$SimpleObjectFactory.getObjectInstance(SimpleReference.java:137) >> >> at >> javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321) >> >> at org.apache.naming.NamingContext.lookup(NamingContext.java:843) >> >> at org.apache.naming.NamingContext.lookup(NamingContext.java:168) >> >> at >> >> >> org.apache.tomee.catalina.TomcatWebAppBuilder.safeBind(TomcatWebAppBuilder.java:1755) >> >> at >> >> >> org.apache.tomee.catalina.TomcatWebAppBuilder.afterStart(TomcatWebAppBuilder.java:1287) >> >> at >> >> >> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:104) >> >> at >> >> >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >> >> at >> >> >> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) >> >> at >> >> >> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402) >> >> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:168) >> >> at >> >> >> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) >> >> at >> >> >> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) >> >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:166) >> >> at >> >> >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) >> >> at >> >> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> >> at java.lang.Thread.run(Thread.java:679) >> >> 01/03/2013 17:04:48 org.apache.tomee.catalina.TomcatWebAppBuilder >> safeBind >> >> SEVERE: Error in safeBind method >> >> javax.naming.NameNotFoundException: No HandleDelegate registered with >> >> the OpenEJB system >> >> at >> >> >> org.apache.openejb.core.ivm.naming.SystemComponentReference.getObject(SystemComponentReference.java:38) >> >> at >> >> >> org.apache.openejb.core.ivm.naming.Reference.getContent(Reference.java:40) >> >> at >> >> >> org.apache.xbean.naming.reference.SimpleReference$SimpleObjectFactory.getObjectInstance(SimpleReference.java:137) >> >> at >> javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321) >> >> at org.apache.naming.NamingContext.lookup(NamingContext.java:843) >> >> at org.apache.naming.NamingContext.lookup(NamingContext.java:168) >> >> at >> >> >> org.apache.tomee.catalina.TomcatWebAppBuilder.safeBind(TomcatWebAppBuilder.java:1755) >> >> at >> >> >> org.apache.tomee.catalina.TomcatWebAppBuilder.afterStart(TomcatWebAppBuilder.java:1288) >> >> at >> >> >> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:104) >> >> at >> >> >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >> >> at >> >> >> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) >> >> at >> >> >> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402) >> >> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:168) >> >> at >> >> >> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) >> >> at >> >> >> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) >> >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:166) >> >> at >> >> >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) >> >> at >> >> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> >> at java.lang.Thread.run(Thread.java:679) >> >> >> >> >> >> Thanks in advance! >> >> >> >> >> >> -- >> Bruno Klava >> -- Bruno Klava
