Hey there,
we're currently reworking our deployment and have switched to EAR with our
project. When starting up our TomEE 1.7.4 applicationserver the deployment
of the EJB projects works flawlessly and without any warnings but the
webapps in the EAR cause the following exceptions in the console:
e.g:
javax.naming.NameAlreadyBoundException: ParsedName{path=GeoCode,
component=GeoCode}
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:158)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:168)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:168)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:168)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.NameNode.bind(NameNode.java:175)
at
org.apache.openejb.core.ivm.naming.IvmContext.bind(IvmContext.java:308)
at
org.apache.openejb.core.ivm.naming.IvmContext.rebind(IvmContext.java:322)
at
org.apache.openejb.assembler.classic.Assembler.bindGlobals(Assembler.java:1188)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1379)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1100)
at
org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:130)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5472)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Our service works without any problems but the errors are a bit annoying. It
seems like the webappbuilder tries to register our EJBs again in the webapps
but fails to do so.
I've searched the net quite a lot and found some threads but none of those
fit our case. I would like to submit a minimal example but i'm afraid to
violate corporate policies. I will try my best to answer any upcoming
questions though!
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
