Re: NameAlreadyBoundException when deploying as EAR

Try adding this to your setenv.sh or changes system.properties accordingly: -Dopenejb.deploymentId.format={appId}/{ejbJarId}/{ejbName} -Dopenejb.wsAddress.format={ejbName} That will make your deployement Id's for EJB's include the app/jar names and won't impact any web service endpoints you may

Re: NameAlreadyBoundException when deploying as EAR

It can if multiple modules deploy the same EJB Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: NameAlreadyBoundException when deploying as EAR

The EJBs lie in their own modules and are only used by the webapps through injection. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: NameAlreadyBoundException when deploying as EAR

Hi if you customized EJB deploymentId with the corresponding property to not be ambiguous accross ear modules/webapps then it can be a bug fixed on the 7.x we never backported. This part was improved quite a lot on 7.x Romain Manni-Bucau @rmannibucau | Blog

Re: NameAlreadyBoundException when deploying as EAR

Are you refering to the openejb.deploymentId.format property? We're currently using the default format. Could this be the root of our problem? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

NameAlreadyBoundException when deploying as EAR

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: