The objects in the EJB module could not be bound as Portable Global JNDI names because there are already modules with the same names under the same application in the naming service. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI
bb....bb: Standard module name

Description

A module in the same application with the same standard module name already exists in the naming service. Therefore, the objects in the EJB module could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

• If there is a client that looks up the objects in this EJB-JAR module using the Portable Global JNDI name.
• If a resource reference is defined in this EJB-JAR module using a name beginning with java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this EJB-JAR module, take the following action to change the standard module name:

If <module-name> of ejb-jar.xml is specified

Change the value specified in <module-name> to another name and then re-import.

If <module-name> of ejb-jar.xml is not specified (if ejb-jar.xml is omitted)

Change the EJB-JAR file name (EJB directory name in the exploded archive format) to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.