The objects in the J2EE application could not be bound as Portable Global JNDI names because there is already an application in the naming service with the same application name. (name = aa....aa, application name = bb....bb)

aa....aa: Application display name
bb....bb: Standard application name

Description

An application with the same standard application name already exists in the naming service. Therefore, the objects in the J2EE application 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 application using the Portable Global JNDI name.
• If a resource reference is defined in this application using a name beginning with java:app or java:module.

Action

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

If <application-name> of application.xml is specified

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

If <application-name> of application.xml is not specified (if application.xml is omitted)

Change the EAR file name (application 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.