When multiple EJB export binding components are bound to the same interface, users may see the exceptions below in the log even if the auto generated JNDI names are modified.
The typical error messages are:
EJBContainerI I WSVR0037I: Starting EJB jar:
BindingsHelpe E CNTR0172E: The <InterfaceName>RemoteInterfaceHome
interface of the <ModuleNameB>_EJBExport_Export_EJB_2 bean in the
<ModuleNameB>_EJBExport_Export_EJB_2.jar module of the <AppNameB>
application cannot be bound to the
.../<InterfaceName>RemoteInterfaceHome name location. The
<InterfaceName>RemoteInterfaceHome interface of the
<ModuleNameA>_EJBExport_Export_EJB_2 bean in the
<ModuleNameA>_EJBExport_Export_EJB_2.jar module of the <AppNameA>
application has already been bound to the
.../<InterfaceName>RemoteInterfaceHome name location.
EJBContainerI E WSVR0039E: Unable to start EJB jar
EJBContainerI I WSVR0041I: Stopping EJB jar:
In this scenario with EJB 2.x the auto generated JNDI name for the remote interface home is the same, which is constructed by <InterfaceName>+"RemoteInterfaceHome", without referencing the user assigned names. As designed, the EJB container will only start one service for a one single JNDI name. As a result the first one can register and start successfully, while the others cannot (they can, however use the same home via the JNDI name without any negative effects).
EJB Container will try to start EJB_2.jar and generate the EJB bindings even if user will not be using EJB v2.x bean in the module.
Although the user has assigned different JNDI names for the export components, in
most situations, however they will be used for the EJB v3 JNDI names.
Resolving the problem
This is working as designed. User can ignore this error.