Re: NameAlreadyBoundException when deploying as EAR

That answers question number 2 but why is the rebind happening at all? The beans already exist and are registered within the context otherwise the error wouldn't be thrown. Shouldn't the webappbuilder just pick up the existing bean and be done with it? I just want to rule out any errors in our

Re: NameAlreadyBoundException when deploying as EAR

Unaltered behaviour. Checked the corresponding source of openejb-core 4.7.4: public void bindGlobals(Map bindings) throws NamingException { Context containerSystemContext = this.containerSystem.getJNDIContext(); for (Map.Entry value : bindings.entrySet())

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

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:

ActiveMQ Websocket Transport in TomEE 7.0.4 possible?

I'm currently trying to setup the ActiveMQ websocket transport for our applicationserver. So far i've added all needed dependencies but the Jettys ServletContainerInitializer annotations seem to cause problems: 2018-12-20 16:14:30,664 [localhost-startStop-1] ERROR