summary deployment error related to what I described before:
DEPLOYMENTS IN ERROR:
=EJB3" is in error due to the following reason(s): org.jboss.ejb3.common.registrar.spi.DuplicateBindException: Cannot install org.jboss.ejb3.proxy.clu
stered.factory.session.stateless.StatelessSessionClusteredProxyFactory@565388 under name "ProxyFactory/prototype_ear-0.1-SNAPSHOT/ServerCmdExecutorBea
n/prj/ServerCmdExecutor/remote/DefaultPartition" as there is already an existing object there: org.jboss.ejb3.proxy.clustered.factory.session.
And of course there are no two jars or ears with the same ejb deployed in jboss. This only happens when I use both annotation: @Clustered and @RemoteBinding.
Unfortunatelly it was my mistake. I was pretty sure there is no second ejb component deployed. And it was almost true, but I missed that maven plugin put the same jar under ear/lib folder, so even if the second jar was not listed in application.xml as ejb module, it was somehow took by jboss deployer. After fixing this seems it works.
And it was almost true, but I missed that maven plugin put the same jar under ear/lib folder, so even if the second jar was not listed in application.xml as ejb module, it was somehow took by jboss deployer.
Just a FYI - The EAR/lib folder is not expected to be scanned for deployments. There's a separate thread tracking this issue http://www.jboss.org/index.html?module=bb&op=viewtopic&t=143590