Re: bootstrap openwebbeans into java se application
Not sure i get you @singleton @startup is not enough? Le 18 sept. 2013 07:36, "mauro2java2011" a écrit : > But i serch for a boot like the following sample > example from weld with obeserve event or weld class > http://antoniogoncalves.org/2011/01/12/bootstrapping-cdi-in-several-environments/ > > > For use owb into a java se application not for test. > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/bootstrap-openwebbeans-into-java-se-application-tp4665109p4665119.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: bootstrap openwebbeans into java se application
http:// http://antoniogoncalves.org/2011/01/12/bootstrapping-cdi-in-several-environments/ http://antoniogoncalves.org/2011/01/12/bootstrapping-cdi-in-several-environments/> Go at section java se -- View this message in context: http://openejb.979440.n4.nabble.com/bootstrap-openwebbeans-into-java-se-application-tp4665109p4665120.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: bootstrap openwebbeans into java se application
But i serch for a boot like the following sample example from weld with obeserve event or weld class http://antoniogoncalves.org/2011/01/12/bootstrapping-cdi-in-several-environments/> For use owb into a java se application not for test. -- View this message in context: http://openejb.979440.n4.nabble.com/bootstrap-openwebbeans-into-java-se-application-tp4665109p4665119.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: scope for jms resource into cdi
Hi Context and queue can be appscoped but other should be requestscoped...excepted you sont have any request so it wouldnt work as expected (will be fixed in next spec version). That said the connection factory can be injected with @resource, then cdi is quite useless... Le 18 sept. 2013 01:12, "mauro2java2011" a écrit : > I would use cdi method producer for get JmsFactory and Queque , > connection > and Session. > I use method @Produces and dispose . > I have write the application jmd > S and deployed at tomee remote. > Now into another tomcat wirh a jsf application i would send a message at > tomee remote. > > I have write a class for produce: > 1) The contextinitial remote ( the context i have to make > @ApplicationScoped?) > > Next i get the ConnectionFactoriJms with a method Producer and like > parameter at method i pass the contecxt) > > 2) the returned ConnectionFactory from the @Producer i have to make > @RequestScoped ??? ) > > 3) the queque also to make it RequestScoped? > > 4) also for the session for create the message ? > 5) the initiial context for the remote jndi it is ok if i declsre > @ApplicationScoped? > > > Or i have open and close it at each request? > > Or > > > > > > > Get the InitialContext with method @Produces > I code with a jndi lookup on context for get the jms resources. > I ask: > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/scope-for-jms-resource-into-cdi-tp4665108.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: org.apache.openjpa.persistence.PersistenceException: null
Hi Note: In tomee on trunk if you list your classes in persistence-unit it is automatically done if the persistence.xml is in meta-inf/persistence.xml Le 18 sept. 2013 04:40, "Leonardo K. Shikida" a écrit : > So just answering myself (openJPA list brought the solution) > > It seems that if I use IBM JVM (J9) in both windows and linux, it works. > > If I use oracle's, then I get the error. > > My persistence.xml does not have > > > > And I get the warning > > WARNING: Creating subclass for "[...]". > This means that your application will be > less efficient and will consume more memory > than it would if you ran the OpenJPA enhancer. > > Additionally, lazy loading will not be > available for one-to-one and many-to-one > persistent attributes in types using field > access; they will be loaded eagerly instead. > > And this procedure is not recommended as stated at > http://openjpa.apache.org/entity-enhancement.html > > "The use of OpenJPA's subclassing support is not recommended, and is > disabled by default in OpenJPA 2.0 and beyond." > > TIA > > > Leo > > > > [] > > Leo > > > On Tue, Sep 17, 2013 at 1:14 PM, Leonardo K. Shikida > wrote: > > > > Hi > > > > I have an tomee 1.5.2 + that runs perfectly on linux, but when I try to > run from windows, it gives me the following error message (see stacktrace) > > > > My doubts are > > > > - what does it mean :-) > > - why only in windows > > - is there any way to deal with this? > > > > My feeling it that it's somehow related to the OpenJPA enhancement > process, but I really don't have a clue here. > > > > TIA > > > > Leo > > > > Exception in thread "main" javax.ejb.EJBException: The bean encountered a > non-application exception; nested exception is: > > > org.apache.openjpa.persistence.PersistenceException: null > > at > > org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:363) > > at > > org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:283) > > at (...)at > > (...) > > Caused by: > org.apache.openjpa.persistence.PersistenceException: null > > at > > org.apache.openjpa.enhance.ClassRedefiner.redefineClasses(ClassRedefiner.java:96) > > at > > org.apache.openjpa.enhance.ManagedClassSubclasser.prepareUnenhancedClasses(ManagedClassSubclasser.java:176) > > at > > org.apache.openjpa.kernel.AbstractBrokerFactory.loadPersistentTypes(AbstractBrokerFactory.java:314) > > at > > org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:238) > > at > > org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:212) > > at > > org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156) > > at > > org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227) > > at > > org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60) > > at > > org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.createEntityManager(ReloadableEntityManagerFactory.java:160) > > at > > org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:115) > > at > > org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:80) > > (...) > > Caused by: java.lang.VerifyError > > at sun.instrument.InstrumentationImpl.retransformClasses0(Native > Method) > > at > > sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:144) > > ... 52 more > > > > [] > > > > Leo >
Re: Failure to start TomEE with JMS Resources
Hi Houston! Looks like the answer might be quite simple and something we could perhaps add a check for -- some validation perhaps. There appears to be a newline in your datasource declaration: JtaManaged = false JdbcDriver = com.mysql.jdbc.Driver JdbcUrl = jdbc:mysql://localhost:3306/test UserName = root Password = Should be: JtaManaged = false JdbcDriver = com.mysql.jdbc.Driver JdbcUrl = jdbc:mysql://localhost:3306/test UserName = root Password = Hope that helps! -David On Sep 11, 2013, at 1:47 PM, Houston Pagtakhan wrote: > Here's my stack trace. It's unclear to me exactly which class cannot be > resolved or found. I had no problems when I simply defined the DataSource. > But I encountered problems when I added the JMS Resources. > > > Sep 11, 2013 3:35:44 PM org.apache.openejb.config.ConfigurationFactory > configureService > > INFO: Configuring Service(id=MyJmsResourceAdapter, type=Resource, > provider-id=Default JMS Resource Adapter) > > Sep 11, 2013 3:35:44 PM org.apache.openejb.config.ConfigurationFactory > configureService > > INFO: Configuring Service(id=MyCF, type=Resource, provider-id=Default JMS > Connection Factory) > > Sep 11, 2013 3:35:44 PM org.apache.openejb.config.ConfigurationFactory > configureService > > INFO: Configuring Service(id=MyQueue, type=Resource, provider-id=Default > Queue) > > Sep 11, 2013 3:35:44 PM org.apache.openejb.util.OptionsLog info > > INFO: Using 'openejb.system.apps=false' > > Sep 11, 2013 3:35:44 PM org.apache.openejb.util.OptionsLog info > > INFO: Using 'openejb.deployments.classpath=false' > > Sep 11, 2013 3:35:44 PM org.apache.openejb.assembler.classic.Assembler > createRecipe > > INFO: Creating TransactionManager(id=Default Transaction Manager) > > Sep 11, 2013 3:35:44 PM org.apache.openejb.assembler.classic.Assembler > createRecipe > > INFO: Creating SecurityService(id=Tomcat Security Service) > > Sep 11, 2013 3:35:44 PM org.apache.openejb.assembler.classic.Assembler > createRecipe > > INFO: Creating Resource(id=MyDS) > > Sep 11, 2013 3:35:44 PM org.apache.openejb.util.OpenEJBErrorHandler > handleUnknownError > > SEVERE: FATAL ERROR: Unknown error in Assembler. Please send the following > stack trace and this message to us...@openejb.apache.org : > > org.apache.xbean.propertyeditor.PropertyEditorException: Unable to resolve > class > > at > org.apache.xbean.propertyeditor.ClassEditor.toObjectImpl(ClassEditor.java:43) > > at > org.apache.xbean.propertyeditor.AbstractConverter.toObject(AbstractConverter.java:86) > > at > org.apache.xbean.propertyeditor.PropertyEditors.getValue(PropertyEditors.java:284) > > at org.apache.xbean.recipe.RecipeHelper.convert(RecipeHelper.java:172) > > at > org.apache.xbean.recipe.ObjectRecipe.extractConstructorArgs(ObjectRecipe.java:592) > > at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:275) > > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > > at > org.apache.openejb.assembler.classic.Assembler.createResource(Assembler.java:1797) > > at > org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:434) > > at org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:353) > > at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:147) > > at org.apache.openejb.OpenEJB.init(OpenEJB.java:292) > > at org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:233) > > at org.apache.tomee.catalina.TomcatLoader.init(TomcatLoader.java:130) > > at > org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:121) > > 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.init(LifecycleBase.java:110) > > at org.apache.catalina.startup.Catalina.load(Catalina.java:633) > > at org.apache.catalina.startup.Catalina.load(Catalina.java:658) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:606) > > at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281) > > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455) > > Caused by: java.lang.ClassNotFoundException: > > at java.lang.Class.forName0(Native Method) > > at java.lang.Class.forName(Class
Re: what signify the code above????? the method bind ("inject", this);????
On Sep 10, 2013, at 9:55 AM, mauro2java2011 wrote: > this signify the object current. > But the first parameter "inject" it is the operation to make? > > exist other value for the first parameter into the method bind ??? This is effectively a workaround. Dependency Injection did not make it into the final version of EJBContainer API that went into the specification. In order to make it work without introducing any OpenEJB-specific API classes that you'd have to use in your test code, we added the convention to call 'bind(Sring, Object)' where the string must be "inject" and the object is an instance of the class that bootstrapped the EJBContainer (called .createEJBContainer() ). As for what other options can be passed into the bind() method, it always must be "inject", but you can pass in: 1. an instance of the class that called EJBContainer.createEJBContainer() 2. any instance of a class annotated with @javax.annotation.ManagedBean -David
Re: org.apache.openjpa.persistence.PersistenceException: null
So just answering myself (openJPA list brought the solution) It seems that if I use IBM JVM (J9) in both windows and linux, it works. If I use oracle's, then I get the error. My persistence.xml does not have And I get the warning WARNING: Creating subclass for "[...]". This means that your application will be less efficient and will consume more memory than it would if you ran the OpenJPA enhancer. Additionally, lazy loading will not be available for one-to-one and many-to-one persistent attributes in types using field access; they will be loaded eagerly instead. And this procedure is not recommended as stated at http://openjpa.apache.org/entity-enhancement.html "The use of OpenJPA's subclassing support is not recommended, and is disabled by default in OpenJPA 2.0 and beyond." TIA Leo [] Leo On Tue, Sep 17, 2013 at 1:14 PM, Leonardo K. Shikida wrote: > > Hi > > I have an tomee 1.5.2 + that runs perfectly on linux, but when I try to run from windows, it gives me the following error message (see stacktrace) > > My doubts are > > - what does it mean :-) > - why only in windows > - is there any way to deal with this? > > My feeling it that it's somehow related to the OpenJPA enhancement process, but I really don't have a clue here. > > TIA > > Leo > > Exception in thread "main" javax.ejb.EJBException: The bean encountered a non-application exception; nested exception is: > org.apache.openjpa.persistence.PersistenceException: null > at org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:363) > at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:283) > at (...)at > (...) > Caused by: org.apache.openjpa.persistence.PersistenceException: null > at org.apache.openjpa.enhance.ClassRedefiner.redefineClasses(ClassRedefiner.java:96) > at org.apache.openjpa.enhance.ManagedClassSubclasser.prepareUnenhancedClasses(ManagedClassSubclasser.java:176) > at org.apache.openjpa.kernel.AbstractBrokerFactory.loadPersistentTypes(AbstractBrokerFactory.java:314) > at org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:238) > at org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:212) > at org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156) > at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227) > at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60) > at org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.createEntityManager(ReloadableEntityManagerFactory.java:160) > at org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:115) > at org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:80) > (...) > Caused by: java.lang.VerifyError > at sun.instrument.InstrumentationImpl.retransformClasses0(Native Method) > at sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:144) > ... 52 more > > [] > > Leo
Re: bootstrap openwebbeans into java se application
Hi Mauro These examples use CDI in JavaSE via the Embedded EJBContainer API which actually works for CDI as well -- in our integration at least. - http://tomee.apache.org/examples-trunk/cdi-basic/README.html Here's a CDI / Java SE example that uses @ApplicationScoped - http://tomee.apache.org/examples-trunk/cdi-application-scope/README.html In terms of @javax.inject.Singleton vs @ApplicationScoped. I'd go with @ApplicationScoped which is far more defined. -David On Sep 17, 2013, at 4:15 PM, mauro2java2011 wrote: > How i can bootstrap oopenwebbeans into a java se application.? > I have searched but not found examples of owb. > > I have read that into owb for se applic i have 3 scopes. > Singleton > Application > Dependent > > I ask : but what it is the difference from singleton and application scope > > > It sound the same think. > > Mauro > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/bootstrap-openwebbeans-into-java-se-application-tp4665109.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE installation errors
I think there is a firewall configuration somewhere that is crashing the application. I've managed to reproduce your issue in an amazon ec2 box ( https://dl.dropboxusercontent.com/u/1459144/tomee-list/tomee-remote-00.png). Currently the GUI uses websockets. Regular http connections and websockets share the same port 80. It turns out that the javascript code can't connect to the server, and it logs an exception stating it ( https://dl.dropboxusercontent.com/u/1459144/tomee-list/tomee-remote-01.png) The Tomee server above is mapped to both 80 (via Apache httpd) and 8080 (Direct access). As soon as I try the port 8080 instead, it gets back to normal. ( https://dl.dropboxusercontent.com/u/1459144/tomee-list/tomee-remote-02.png) Can you check if that works for you too? Error code 400 (Bad request) http://www.checkupdown.com/status/E400.html []s, Thiago. On Tue, Sep 17, 2013 at 12:04 PM, Thiago Veronezi wrote: > I guess it is a real bug. > I will verify it. > > > > On Tue, Sep 17, 2013 at 11:56 AM, mathiver wrote: > >> Still the same problem with the snapshot version: no errors in the log, >> but a >> "connection exception" when I go to the URL in the browser... More ideas? >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665104.html >> Sent from the OpenEJB User mailing list archive at Nabble.com. >> > >
bootstrap openwebbeans into java se application
How i can bootstrap oopenwebbeans into a java se application.? I have searched but not found examples of owb. I have read that into owb for se applic i have 3 scopes. Singleton Application Dependent I ask : but what it is the difference from singleton and application scope It sound the same think. Mauro -- View this message in context: http://openejb.979440.n4.nabble.com/bootstrap-openwebbeans-into-java-se-application-tp4665109.html Sent from the OpenEJB User mailing list archive at Nabble.com.
scope for jms resource into cdi
I would use cdi method producer for get JmsFactory and Queque , connection and Session. I use method @Produces and dispose . I have write the application jmd S and deployed at tomee remote. Now into another tomcat wirh a jsf application i would send a message at tomee remote. I have write a class for produce: 1) The contextinitial remote ( the context i have to make @ApplicationScoped?) Next i get the ConnectionFactoriJms with a method Producer and like parameter at method i pass the contecxt) 2) the returned ConnectionFactory from the @Producer i have to make @RequestScoped ??? ) 3) the queque also to make it RequestScoped? 4) also for the session for create the message ? 5) the initiial context for the remote jndi it is ok if i declsre @ApplicationScoped? Or i have open and close it at each request? Or Get the InitialContext with method @Produces I code with a jndi lookup on context for get the jms resources. I ask: -- View this message in context: http://openejb.979440.n4.nabble.com/scope-for-jms-resource-into-cdi-tp4665108.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE installation errors
Still the same problem with the snapshot version: no errors in the log, but a "connection exception" when I go to the URL in the browser... More ideas? -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665104.html Sent from the OpenEJB User mailing list archive at Nabble.com.
org.apache.openjpa.persistence.PersistenceException: null
Hi I have an tomee 1.5.2 + that runs perfectly on linux, but when I try to run from windows, it gives me the following error message (see stacktrace) My doubts are - what does it mean :-) - why only in windows - is there any way to deal with this? My feeling it that it's somehow related to the OpenJPA enhancement process, but I really don't have a clue here. TIA Leo Exception in thread "main" javax.ejb.EJBException: The bean encountered a non-application exception; nested exception is: org.apache.openjpa.persistence.PersistenceException: null at org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:363) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:283) at (...)at (...) Caused by: org.apache.openjpa.persistence.PersistenceException: null at org.apache.openjpa.enhance.ClassRedefiner.redefineClasses(ClassRedefiner.java:96) at org.apache.openjpa.enhance.ManagedClassSubclasser.prepareUnenhancedClasses(ManagedClassSubclasser.java:176) at org.apache.openjpa.kernel.AbstractBrokerFactory.loadPersistentTypes(AbstractBrokerFactory.java:314) at org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:238) at org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:212) at org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156) at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227) at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60) at org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.createEntityManager(ReloadableEntityManagerFactory.java:160) at org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:115) at org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:80) (...) Caused by: java.lang.VerifyError at sun.instrument.InstrumentationImpl.retransformClasses0(Native Method) at sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:144) ... 52 more [] Leo
Re: TomEE installation errors
I guess it is a real bug. I will verify it. On Tue, Sep 17, 2013 at 11:56 AM, mathiver wrote: > Still the same problem with the snapshot version: no errors in the log, > but a > "connection exception" when I go to the URL in the browser... More ideas? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665104.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: TomEE installation errors
https://repository.apache.org/content/groups/snapshots/org/apache/openejb/tomee-webapp/1.6.0-SNAPSHOT/ for the web profile version and https://repository.apache.org/content/groups/snapshots/org/apache/openejb/tomee-plus-webapp/1.6.0-SNAPSHOT/ for the plus version Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/17 mathiver : > Hi Thiago, > > Where can I find a snapshot version of the drop-in war? > > Thanks, > > Mathias > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665102.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE installation errors
Hi Thiago, Where can I find a snapshot version of the drop-in war? Thanks, Mathias -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665102.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Failure running webapp in root context with TomEE 1.5.2
Hi not fully sure but maybe have a look to https://issues.apache.org/jira/browse/TOMEE-902, globally the part related was rewritten and I'm not sure you can backport a single commit but you can surely backport more or less the OpenEJBContextConfig class directly. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/17 Jim Ancona : > I've been trying to run my application WAR file in TomEE in the root > context, but it fails with the following exception at startup: > > Sep 17, 2013 10:57:51 AM org.apache.openejb.assembler.classic.Assembler > createApplication > INFO: Deployed > Application(path=/opt/cc/tomee/trackingsvc_tomee/webapps/trackingsvc_tomee) > Sep 17, 2013 10:57:51 AM org.apache.catalina.core.ContainerBase > startInternal > SEVERE: A child container failed during start > java.util.concurrent.ExecutionException: > org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123) > at > org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > 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:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: org.apache.catalina.LifecycleException: Failed to start > component > [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) > ... 7 more > Caused by: java.lang.IllegalArgumentException: can't find path under > current webapp deployment [] > at > org.apache.tomee.catalina.OpenEJBContextConfig.processAnnotationsUrl(OpenEJBContextConfig.java:382) > at > org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1307) > at > org.apache.tomee.catalina.OpenEJBContextConfig.webConfig(OpenEJBContextConfig.java:273) > at > org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878) > at > org.apache.tomee.catalina.OpenEJBContextConfig.configureStart(OpenEJBContextConfig.java:83) > at > org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5179) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > ... 7 more > > The app deploys in the root context with the same configuration in > 1.6.0-SNAPSHOT. It does not deploy in 1.5.3-SNAPSHOT. > > My questions: > * Is there any workaround to get a WAR app to deploy in the root context in > 1.5.2? > * Is there a Jira issue with an associated patch and/or commit that fixes > the issue that I might be able to cherry-pick back into 1.5.2? > > Thanks in advance for any help! > > Jim
Failure running webapp in root context with TomEE 1.5.2
I've been trying to run my application WAR file in TomEE in the root context, but it fails with the following exception at startup: Sep 17, 2013 10:57:51 AM org.apache.openejb.assembler.classic.Assembler createApplication INFO: Deployed Application(path=/opt/cc/tomee/trackingsvc_tomee/webapps/trackingsvc_tomee) Sep 17, 2013 10:57:51 AM org.apache.catalina.core.ContainerBase startInternal SEVERE: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) 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:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) ... 7 more Caused by: java.lang.IllegalArgumentException: can't find path under current webapp deployment [] at org.apache.tomee.catalina.OpenEJBContextConfig.processAnnotationsUrl(OpenEJBContextConfig.java:382) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1307) at org.apache.tomee.catalina.OpenEJBContextConfig.webConfig(OpenEJBContextConfig.java:273) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878) at org.apache.tomee.catalina.OpenEJBContextConfig.configureStart(OpenEJBContextConfig.java:83) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5179) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 7 more The app deploys in the root context with the same configuration in 1.6.0-SNAPSHOT. It does not deploy in 1.5.3-SNAPSHOT. My questions: * Is there any workaround to get a WAR app to deploy in the root context in 1.5.2? * Is there a Jira issue with an associated patch and/or commit that fixes the issue that I might be able to cherry-pick back into 1.5.2? Thanks in advance for any help! Jim
Re: TomEE installation errors
I've checked with trunk and it seems to work. As Romain said, it looks like it was broken for locations other than "localhost". Can you test it with the trunk version just to check if it works now? https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.6.0-SNAPSHOT/ []s, Thiago. On Tue, Sep 17, 2013 at 9:28 AM, mathiver wrote: > Hi, > > I cannot use it from localhost, since I don't have direct GUI access to the > server, so I'm going to > > www.servername.com/tomee > > (where www.servername.com is the server address). > > I'm using Firefox as browser on Linux. > > Best, > > Mathias > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665098.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: TomEE installation errors
Hi, I cannot use it from localhost, since I don't have direct GUI access to the server, so I'm going to www.servername.com/tomee (where www.servername.com is the server address). I'm using Firefox as browser on Linux. Best, Mathias -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665098.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE installation errors
Can you check the browser console and see you you have any logged exception there? Whats you browser? []s, Thiago. On Tue, Sep 17, 2013 at 8:09 AM, Romain Manni-Bucau wrote: > Hi > > if you speak about the tomee gui it was broken if not used from > localhost i think. > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2013/9/17 mathiver : > > Hi, > > > > Ok, so now I don't get any errors in the logs anymore, but the screen > still > > says "Connection exception - The application is waiting for the server." > > > > Any ideas what could still be wrong? > > > > Thanks, > > > > Mathias > > > > > > > > -- > > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665095.html > > Sent from the OpenEJB User mailing list archive at Nabble.com. >
Re: TomEE installation errors
Hi if you speak about the tomee gui it was broken if not used from localhost i think. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/17 mathiver : > Hi, > > Ok, so now I don't get any errors in the logs anymore, but the screen still > says "Connection exception - The application is waiting for the server." > > Any ideas what could still be wrong? > > Thanks, > > Mathias > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665095.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE installation errors
Hi, Ok, so now I don't get any errors in the logs anymore, but the screen still says "Connection exception - The application is waiting for the server." Any ideas what could still be wrong? Thanks, Mathias -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665095.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE installation errors
Hi it is in tomcat itself, if not you use a too old tomcat version i think. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/17 mathiver : > Hi Romain, > > And how do I need to install that (since that dependency isn't on the TomEE > drop-in war install page)? Is that also a war that need to be placed > somewhere? > > Thanks, > > Mathias > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665093.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE installation errors
Hi Romain, And how do I need to install that (since that dependency isn't on the TomEE drop-in war install page)? Is that also a war that need to be placed somewhere? Thanks, Mathias -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-installation-errors-tp4665081p4665093.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE installation errors
Hi means you don't have tomcat-jdbc or it is in your app too. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/17 mathiver : > Hi all, > > I deployed it on a Tomcat 7 instance, but now I get the following error. Any > idea what could be wrong here? > > Sep 17, 2013 11:19:32 AM org.apache.openejb.assembler.classic.Assembler > createRecipe > INFO: Creating Resource(id=My DataSource) > Sep 17, 2013 11:19:32 AM org.apache.openejb.util.OpenEJBErrorHandler > handleUnknownError > SEVERE: FATAL ERROR: Unknown error in Assembler. Please send the following > stack trace and this message to us...@openejb.apache.org : > org.apache.xbean.recipe.ConstructionException: Error invoking factory > method: public static javax.sql.DataSource > org.apache.openejb.resource.jdbc.DataSourceFactory.create(java.lang.String,boolean,java.lang.Class,java.lang.String,org.apache.openejb.util.Duration,org.apache.openejb.util.Duration,org.apache.openejb.util.Duration) > throws > java.lang.IllegalAccessException,java.lang.InstantiationException,java.io.IOException > at > org.apache.xbean.recipe.ReflectionUtil$StaticFactory.create(ReflectionUtil.java:1006) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) > at > org.apache.openejb.assembler.classic.Assembler.createResource(Assembler.java:1797) > at > org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:434) > at > org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:353) > at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:147) > at org.apache.openejb.OpenEJB.init(OpenEJB.java:292) > at > org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:233) > at org.apache.tomee.catalina.TomcatLoader.init(TomcatLoader.java:130) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.apache.openejb.loader.Embedder.init(Embedder.java:77) > at org.apache.tomee.loader.TomcatHook.hook(TomcatHook.java:173) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.tomee.loader.TomcatEmbedder.embed(TomcatEmbedder.java:100) > at org.apache.tomee.loader.LoaderServlet.init(LoaderServlet.java:66) > at > org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266) > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185) > at > org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080) > at > org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5015) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5302) > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615) > at > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:958) > at > org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1599) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > 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) > Caused by: java.lang.NoClassDefFoundError: > org/apache/tomcat/jdbc/pool/PoolProperties > at > org.apache.tomee.jdbc.TomEEDataSourceCreator.pool(TomEEDataSourceCreator.java:80) > at > org.apache.openejb.resource.jdbc.pool.PoolDataSourceCreator.poolManaged(PoolDataSourceCreator.java:64) > at > org.apache.o
Re: TomEE installation errors
Hi all, I deployed it on a Tomcat 7 instance, but now I get the following error. Any idea what could be wrong here? Sep 17, 2013 11:19:32 AM org.apache.openejb.assembler.classic.Assembler createRecipe INFO: Creating Resource(id=My DataSource) Sep 17, 2013 11:19:32 AM org.apache.openejb.util.OpenEJBErrorHandler handleUnknownError SEVERE: FATAL ERROR: Unknown error in Assembler. Please send the following stack trace and this message to us...@openejb.apache.org : org.apache.xbean.recipe.ConstructionException: Error invoking factory method: public static javax.sql.DataSource org.apache.openejb.resource.jdbc.DataSourceFactory.create(java.lang.String,boolean,java.lang.Class,java.lang.String,org.apache.openejb.util.Duration,org.apache.openejb.util.Duration,org.apache.openejb.util.Duration) throws java.lang.IllegalAccessException,java.lang.InstantiationException,java.io.IOException at org.apache.xbean.recipe.ReflectionUtil$StaticFactory.create(ReflectionUtil.java:1006) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.apache.openejb.assembler.classic.Assembler.createResource(Assembler.java:1797) at org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:434) at org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:353) at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:147) at org.apache.openejb.OpenEJB.init(OpenEJB.java:292) at org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:233) at org.apache.tomee.catalina.TomcatLoader.init(TomcatLoader.java:130) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.openejb.loader.Embedder.init(Embedder.java:77) at org.apache.tomee.loader.TomcatHook.hook(TomcatHook.java:173) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.tomee.loader.TomcatEmbedder.embed(TomcatEmbedder.java:100) at org.apache.tomee.loader.LoaderServlet.init(LoaderServlet.java:66) at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5015) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5302) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:958) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1599) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 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) Caused by: java.lang.NoClassDefFoundError: org/apache/tomcat/jdbc/pool/PoolProperties at org.apache.tomee.jdbc.TomEEDataSourceCreator.pool(TomEEDataSourceCreator.java:80) at org.apache.openejb.resource.jdbc.pool.PoolDataSourceCreator.poolManaged(PoolDataSourceCreator.java:64) at org.apache.openejb.resource.jdbc.DataSourceFactory.create(DataSourceFactory.java:118) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.xbean.recipe.ReflectionUtil$StaticF
