My Oracle Support Banner

javax.naming.NameAlreadyBoundException: [EJB:011224]Unable to bind the interface - JNDI naming collision occurs when two separate applications, EAR and WAR, have the same exact EJB (Doc ID 1642388.1)

Last updated on MAY 01, 2023

Applies to:

Oracle WebLogic Server - Version 12.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

After the WLS 12c upgrade from 10.3.6, we are seeing issues where a domain comes up on Admin mode. Majority of the errors on the server log points to the issue of failing to bind business Interface to the JNDI name due to the fact that another EJB had already bound an interface to that name.

In WLS 12c, a JNDI naming collision occurs when two separate applications, EAR and WAR, have the same exact EJB:

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.